From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: linux-kernel@vger.kernel.org
Subject: [CFT] 2.6.9-rc2-bk1-bird1 patchset
Date: Wed, 17 Nov 2004 15:05:08 +0000 [thread overview]
Message-ID: <20041117150508.GD26051@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20041020233547.GN23987@parcelfarce.linux.theplanet.co.uk>
News:
* based on 2.6.10-rc2-bk1 now
* a bunch of patches got merged - some into Linus' tree, some into
bk-net
* iomem patches in sound/oss
* eicon patchset added; that one is *not* for merge until maintainer
ACKs the sucker
* more __user annotations for recently merged stuff (folks, please
at least try to run make C=2 after your patches and look for regressions).
* misc iomem annotations and fixes all over the place in drivers/*
Currently patch is on
ftp.linux.org.uk/pub/people/viro/patch-2.6.10-rc2-bk1-bird1.bz2. Splitup is
in ftp.linux.org.uk/pub/people/viro/patchset/.
Added chunks:
X6 alpha-numa CONFIG_NUMA is broken on alpha right now
X11 emu10k-ioctl CONFIG_EMU10K1 is broken on a shitload of platforms
U573 pc300 portability fixes for pc300
X15 xircom fix for botched MODULE_PARM conversion in xircom
U574 i2o i2o iomem annotation
U575 cpq cpqphp_nvram iomem annotation
U576 misc_user trivial __user annotations
U577 init more C99 initializers
U578 w1 drivers/w1 iomem annotations
U579 isdn more trivial isdn iomem annotations
U580 pcilynx pcilynx iomem annotations
U581 media trivial drivers/media iomem annotations
U582 oss sound/oss iomem annotations
U583 ad1889 ad1889 iomem annotations and leak fixes
U584 64bit misc portability fixes
U585 sound_pci sound/pci iomem annotations
U586 isdn_fix isdn/pcbit iomem fix
U587 zoran_fix zoran iomem fix
U588 imsttfb imsttfb iomem annotations
U589 tgafb tgafb iomem annotations
U590 i386_uaccess i386 uaccess.h annotations
X20 config-rio marks rio broken
EIC1 eicon_getword distinguish between iomem and normal memory access
# adds new helpers ({GET,PUT}_{WORD,DWORD}) parallel to READ_WORD et.al.,
# but used on normal memory instead of iomem. Instances of READ_WORD
# and friends that are applied to vmalloc'ed memory and local variables
# switched to new helpers.
EIC2 eicon_iomem eicon iomem annotations
EIC3 eicon_readb eicon byte iomem access fixes
# new helpers - READ_BYTE() and WRITE_BYTE(). On Linux they are needed, since
# direct access to iomem pointers is not allowed (and does not work on some
# architectures).
# memcpy() to/from iomem is not allowed on Linux (same story). Proper
# primitives are memcpy_toio() and memcpy_fromio(). Several places
# misused memcpy(); switched to memcpy_{to,from}io().
EIC4 eicon_fix s_4bri.c bugfix (bogus &)
# s_4bri.c has a nasty typo - bogus & in qBri_cpu_trapped().
# We have
# void *base;
# followed by
# regs[0] = READ_DWORD((&base + offset) + 0x70);
# which is *NOT* what is meant there - instead of access to memory pointed to
# by base we get access to _stack_ at some offset from the place where the
# local variable base lives.
prev parent reply other threads:[~2004-11-17 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 0:52 [CFT] 2.6.9-rc4-bird1 patchset viro
2004-10-18 2:06 ` [CFT] 2.6.9-rc4-bird2 patchset viro
2004-10-20 23:35 ` [CFT] 2.6.9-bk4-bird1 patchset viro
2004-11-17 15:05 ` Al Viro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041117150508.GD26051@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome