Patch from Ben LaHaise and Bill Irwin.

As discussed a month or so ago, all parties agree that the new
hugetlbfs and shm APIs are sufficient for the 2.6 kernel.

I marked the vacated syscall slots as "available for reuse".  I doubt
that there will be any conflicts when that happens.

Remove unused task_struct.swappable.

Some workloads (Oracle...) use a huge number of VMA's.  They are
currently a tidy 64 bytes in size, and padding them out to 128 on P4's
is not worthwhile.

Patch from Ravikiran G Thirumalai <kiran@in.ibm.com>

Creates a simple "kmalloc for each CPU" API.  This will be used for net
statistics, disk statistics, etc.  (davem has acked the net patches which use
this code).

kmalloc_per_cpu() is available to modules, unlike the current static per-cpu
infrastructure.

swsusp gets confused when pages which it freed do not appear in the
buddy lists.  So provide a function which will drain the calling CPU's
per-cpu-pages into the buddy.

The patch has been tested by Pavel.  Presence of the new code is
conditional on CONFIG_SOFTWARE_SUSPEND.

Patch from Mark Fasheh <mark.fasheh@oracle.com>

A missing chunk from the semtimedop() implementation.  It enables
semtimedop() for 32-bit ia32 applications running on ia64.

It also changes semop() to go direct to sys_semtimedop(), bypassing a
function call.

Cleanup patch from Hollis Blanchard <hollis@austin.ibm.com>

We have a large number of private implementations of BIN_TO_BCD and
BCD_TO_BIN, which are all the same.  And a lot of them are inflexible because
they modify their arg:

	#define BIN_TO_BCD(val) ((val)=(((val)/10)<<4) + (val)%10)

- Create (in <linux/bcd.h> a generic BIN2BCD/BCD2BIN which does not modify
  its arg

- Create generic BIN_TO_BCD/BCD_TO_BIN which uses the above

- Update lots of callers to use the new generic version.

It seems to have been displaying zero for the past several years, and
we can't think of anything useful to put in there.

Patch from Paul Jakma <paulj@alphyra.ie>

Documentation/sysctl/fs.txt is incorrect wrt to the middle number of
/proc/sys/fs/file-nr.  The current docs state it is the number of
in-use file-handles, from observation this number is actually the
number of /unused/ file-handles - we've observe that when it hits 0 we
get file handle problems (rather than when it hits == file-max as docs
imply).

Turns out there was an undocumented "c" flag for MODULE_PARM.

This implementation is a little ugly, but it works, and will do for
compatibility (I haven't implemented such a two-dimensional array
primitive, but the whole point of the module_parm et al is that they are
extensible).

The name is just a bit too generic, and we already use the _X86 prefix
for lots of other stuff in that area.  Dito for the never use CONFIG_PC
and CONFIG_VISWS.

This patch combines my patch which statically initialises the crc32
tables so they can be used at any time (during initialisation) and
Joakim Tjernlund's patch to speed up the crc calculations by doing word
operations instead of exclusively byte.

The crc routines are used extensively in jffs2 where speed is very
important.

I need the crc32 routines to calculate a checksum on values read from an
eeprom which contain cpu speed and memory size information - so they are
needed very much earlier in the initialisation process than they are
currently available.

Clean up searching for best frequency, and add one safety check.

Clean up searching code for best frequency and add some safety checks.

The usage of CPUFREQ_ALL_CPUS is deprecated. Only exception is cpufreq_set,
which needs to iterate over all CPUS now. Also, remove some unneeded code.

into home.transmeta.com:/home/torvalds/v2.5/linux

Here is my multiple-bug-fix patch for the ide-tape driver.

The corresponding patch for 2.4.21 has already been accepted by Marcelo.

We restore the ","s after parsing: if expect to keep pointers to this
stuff, we must not do that.

NUMAQ does not link - it wants the smp_read_mpc_oem() which I recently disabled.

completly remove the old try_inc_mod_count()

* i2c-elektor.h is empty except for comments
* sensors.h contains register offsets for tons of hw monitoring chips,
  move the few we actually need into the two drivers that use it
  (there is _no_ overlap)

a few new ids, a name change and 10 lines of new code, ported over from
the external i2c package.

Add a struct module *owner field to struct i2c_adapter and i2c_algorithm
and do refcouting on them before use instead of the inc_use and dec_use
callbacks.  While at it convert those structures to named initializers.

into raven.il.steeleye.com:/home/jejb/BK/scsi-for-linus-2.5

into home.transmeta.com:/home/torvalds/v2.5/linux

Expose declaration of __this_module outside #ifdef KBUILD_MODNAME
(which is not defined for objects included in two modules).

I interpreted "1-10s" to mean a string of 1-10 chars.  It actually
means 1-10 comma-separated strings.

Kernel codingsyle explicitly forbids it.  Fortunately there aren't many
useres left.

into kroah.com:/home/linux/linux/BK/tty-2.5

Also got rid of the unused flag paramater.

Currently for block devices both the SCSI_IOCTL_GET_IDLUN and 
SCSI_IOCTL_GET_BUS_NUMBER ioctls yield the value 0 (type: int).

Various applications that utilize the sg driver use these ioctls
to work out the relationship between sg devices and their higher
level counterparts in the sd, sr, st and osst drivers. Examples
that spring to mind are cdrecord, cdparanoia, SANE and sg_utils.

This has been discussed in an earlier threaded started by me:
http://marc.theaimsgroup.com/?l=linux-scsi&m=103967899608891&w=2
in which my patch removed the ioctls in question from the block
level. This broke non-scsi block devices that used applications
that thought they were talking to an sg device **.

The attachment fine tunes the original patch: for scsi block
devices (i.e. owned by the sd or sr drivers) these 2 ioctls
are redirected to the scsi mid level; for non-scsi block
devices they will yield the value as 0 as they do now in
lk 2.5.53 .


** This "yield 0" strategy will come unstuck when 2 or more
cd writers (for example) are connected to the same box.
Hence to be well formed, these ioctls (together) should
produce unique tuples for each device (be they ATA(PI) or
SCSI).

this is only for the module-related warning introduced by my
__deprecated patch.

journal_init_common is always called from ext3 which already makes
jbd.ko unloadable by relying on exported functions.