into touki.austin.ibm.com:/home/jgrimm/bk/lksctp-2.5.work

Support pushing a partial record up to the application if we 
are receiving pressure on rwnd.  The most common case is that
the sender is sending a record larger than our rwnd.  We send 
as much up the receive queue in hopes that a read will occur 
up room in rwnd. 

Other associations on the socket need held off until the partial 
delivery condition is finally fufilled (or ABORTed).  Additionally, 
one must be careful to "do the right thing" with regards to 
associations peeled off to new sockets, properly preserving or 
clearing the partial delivery state.

into us.ibm.com:/home/sridhar/BK/lksctp-2.5.60

Most of the instances of <module>.o in Kconfig files have had the ".o"
extension trimmed.  This change came from GertJan Spoelman through Rusty
"Trivial" Russell.

However, there are a few files that didn't get trimmed.  This brings
them line with the rest of the tree.

so that there isn't any window for running before the signal
handler has been invoced.

from certain states.

This simplifies "default_wake_function()", and makes it possible for
signal handling to wake up only the processes it _should_ wake up
without races.

From:  GertJan Spoelman <kl@gjs.cc>

  OK, here is a new patch, I edited the old patch and took out the .ko's
  so now the extension is trimmed instead.

[ Acked by AKPM --RR ]
From:  Kazuto MIYOSHI <miyoshi@hpc.bs1.fc.nec.co.jp>

  On 64-bit platforms, issuing write(2) with buffer larger than
  2GB will return -1 and broken errno (such as 2147483640)
  Requested data itself is written correctly.

  That is because generic_file_write() and other relating functions
  store 'ssize_t written' into 'int err'. Written byte is trimmed to
  int and then sign-extended to a negative ssize_t value, which
  wrongly indicates an error.

  (On 64bit platform, current glibc defines SSIZE_MAX as 'LONG_MAX')

From:  Steven Cole <elenstev@mesatop.com>

  Here are some help texts from 2.4.21-pre3 Configure.help which are
  needed in 2.5.59 drivers/media/video/Kconfig.

From:  Pablo Menichini <pablo@menichini.com.ar>

From:  Steven Cole <elenstev@mesatop.com>

  Here are some help texts from 2.4.21-pre3 Configure.help which are
  needed in 2.5.59 drivers/char/watchdog/Kconfig.

From:  Steven Cole <elenstev@mesatop.com>

  Here are some help texts from 2.4.21-pre3 Configure.help which are
  needed in 2.5.59 drivers/ide/Kconfig.

From:  Pavel Machek <pavel@ucw.cz>

  This patch makes kernel ignore bad signature on suspend device when
  "noresume" is given, and cleans things up a little bit. Please apply,

[ Verified that no text changed with tr and cmp --RR ]
From:  ookhoi@humilis.net

  With this patch I tried to make Documentation/arm/SA1100/CERF more
  readible by fixing the linewrap.

From:  Steven Cole <elenstev@mesatop.com>

  This fixes the only instance of "kernal" in 2.5.59.

From:  David Gibson <david@gibson.dropbear.id.au>

  is never used, so this patch removes it.

From:  William Lee Irwin III <wli@holomorphy.com>

  This trivially corrects an unused variable warning in nfs/write.c:

From:  Adrian Bunk <bunk@fs.tum.de>

  drivers/net/tulip/de4x5.h in 2.5.54 contains a definition of
  LinuxVersionCode. LinuxVersionCode isn't used and it's anyway obsoleted
  by KERNEL_VERSION in version.h.

From:  Pavel Machek <pavel@ucw.cz>

  Second part of this patch never got in (and I was told it was not bug
  in ASUS but in linux), so it is useless junk... Please apply,

From:  Pablo Menichini <pablo@menichini.com.ar>

  	This patch returns correct error codes if init_modules fail.
  Because of this, we can take the printks indicating the error as these
  corrected error codes return miningfull information.

From:  Pablo Menichini <pablo@menichini.com.ar>

(Included in 2.4)
From:  Paul Gortmaker <p_gortmaker@yahoo.com>

  Summary: Wildcards in RTC alarm settings failed to work

  Description:
   The RTC has provision for wildcards when setting the alarm; to
   use them you have to write a value higher than 0xc0 to the
   appropriate hr/min/sec entry.  The driver used 0xff, which is
   fine, but it mistakenly fed the 0xff through BIN_TO_BCD before
   writing them (which is < 0xc0) and so wildcards didn't work.
   (Thanks to Gerhard Kurz for reporting the bug.)

From:  Pablo Menichini <pablo@menichini.com.ar>

From:  Muli Ben-Yehuda <mulix@mulix.org>

  The i2c driver_lock is needlessly exported.
  This makes it static.

From:  Bob Miller <rem@osdl.org>

  Include string.h to remove a compiler warning.

From:  Steven Cole <elenstev@mesatop.com>

  Here are some help texts from 2.4.21-pre3 Configure.help which are
  needed in 2.5.59 drivers/i2c/Kconfig.

From:  Pablo Menichini <pablo@menichini.com.ar>

From:  Frank Davis <fdavis@si.rr.com>

     The ver_linux script is still using rmmod to determine
  module-init-tools version. The following patch uses depmod,
  which produces the appropriate result.

From:  Steven Cole <elenstev@mesatop.com>

  Here is a help text from 2.4.21-pre4 Configure.help which is
  needed in 2.5.59 drivers/atm/Kconfig.

From:  Pablo Menichini <pablo@menichini.com.ar>

From:  Geert Uytterhoeven <geert@linux-m68k.org>

  parport_pc_pnp_driver is const if !CONFIG_PNP, while pnp_register_driver()
  takes a non-const pointer as parameter.

  An alternative fix is to change the prototype of the dummy
  pnp_register_driver(), but this may affect other drivers.

From:  william stinson <wstinson@wanadoo.fr>

  this patch for drivers/net/irda/irport.c IRDA driver removes one call
  to check_region using request_region instead.  The patch also moves
  the call to request_region to before the allocation of the driver
  instance.

From:  John Levon <levon@movementarian.org>

From:  John Bradford <john@grabjohn.com>

From:  Frank Davis <fdavis@si.rr.com>

  this was already mentioned on l-k by ramune@net-ronin.org, but isn't in
  2.5.59. Placing on the trivial queue for inclusion.

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

return an error.

Interestingly, nobody much seems to care. Apparently few programs
check the error value.

them do want to temporarily block signals.

Kernel users can also block signals that are normally unblockable
to user space, ie SIGKILL and SIGSTOP.

Make nfsd and autofs use the new interface, as an example to others. 

Do not crash on null pointer dereference, if cannot reread superblock.