(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.

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

  - a read_lock(&tasklist_lock) is missing around the group_send_sig_info()
    in send_sig_info().

 - session-IDs and group-IDs are set outside the tasklist lock. This
   causes breakage in the USB code. The correct fix is to do this:

I introduced the bug with the new pidhash.

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

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

into samba.org:/scratch/anton/sfr

into samba.org:/scratch/anton/sfr

  - moved inclusion of <linux/interrupt.h> from <sound/asound.h> to <sound/timer.h>
  - pmac driver - removed beep stuff for 2.5 kernels
  - USB driver - fixed compilation

We have 53c700.c and 53c7xx for the 7xx series and
ncr53c8xx for the 720.  The sym53c8xx_2 covers all the 8xx chips.

It's probably going to be a fifo, so it should be more efficient
for taking them off again

This should add synchronous support and Tagged Command Queueing.
At the moment, it cuts down on the number of command line options,
but we can add those back in later.

This patch also migrates the driver to the new device model for
both MCA and EISA.

The recent slab allocation changes mean that we no longer keep a
permanent list of commands on the device_queue list.  However,
certain pieces of SCSI code relied on being able to traverse this
list to find details of all outstanding commands (the error handler
being the prime example).  This code adds back a new dynamic cmd_list
which keeps the list of commands currently allocated to the device.
Since the list is dynamic, it is protected by a lock (list_lock).

into kernel.bkbits.net:/home/davem/net-2.5

If CONFIG_PREEMPT is enabled, and the kernel is preempted just before
do_debug() has a chance to save the debug register values, DR6 could be
read from the wrong CPU.

It is exactly the same problem as reading %cr2 in the page fault
handler.  Same fix: make the handler a interrupt gate, and enable
interrupts only once safe.

sys_exit_group() doesn't return any value, and obviously cannot.

So don't make the compiler unhappy about it by claiming it does.

Fix wrong order of process status. It's

	#define TASK_RUNNING            0
	#define TASK_INTERRUPTIBLE      1
	#define TASK_UNINTERRUPTIBLE    2
	#define TASK_STOPPED            4
	#define TASK_ZOMBIE             8
	#define TASK_DEAD               16

but SysRQ printout routines switch stopped and zombie around.

So, for one more time, here's another mailing of the same patch to fix
this brokenness.  In addition, fix the wrong comment in fs/proc/array.c

This fixes the signal code to not wake up threads with blocked signals,
especially noticeable with kernel threads that may not be able to handle
signals at all.

We also don't unnecessarily wake processes in TASK_UNINTERRUPTIBLE.