into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.isdn

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

- Make the ide-cd driver usable again in DMA mode by adapting it to the TCQ
   related request handling changes and fixing some other minor stuff related to
   this. This patch is ugly like hell I know. Cleanup will follow separately.
   It was hard enough to make this going agian at all.

in /etc/kernel-config, and only if that fails in the architecture-
specific defconfig.

USB fix documentation bug

 After some source investigations I discovered a harmless mistake:
 The description of the  usb_control_msg(...) function says
 it returns 0, or less than 0 if an error occured, but
 the usb_internal_control_msg returns length, which is sometimes >0
 (success) or <0 if error.

was already done based on CPU capabilities at run-time

Oh, and for non-x86 platforms with interesting pci
mapping, this tweak to one new routine would be
important in a particular error path I've yet to see ... :)

It fixes problems with interrupt transfers, which I think that
nobody else has run into (or I'd surely have heard of it :).
Looks like not many folk are using USB 2.0 hubs yet.

    - wasn't checking enough of the periodic schedule to
      detect bandwidth overcommit (would BUG out)
    - frames to uframes is rightshift 3, not 8 :)
    - properly cleans up (no oops!) after certain rare errors
      in the interrupt submit path (just my luck to hit one)
    - use that cleanup to bypass some old implementation
      shortcuts in the control and bulk submit paths
    - there are also some other minor updates/cleanups

  
  general cleanups:
  	- removed commented out function prototypes
  	- removed duplicate function prototypes
  	- removed unneeded #include
  	- added named initializers
  	- merged lots of the individual device structures into general 1, 2, and 4 port structures.

vda@port.imtp.ilyichevsk.odessa.ua: SAK messages:
  I use SAK from time to time when I have problems with hung processes.

  Sometimes it is difficult to figure out what was being killed and why.

  For example, Midnight Commander contains a bug: it holds fd#3 open to
  the tty. It prevented me from daemonizing processes (like X) - they
  died upon SAK.

  This little patch makes SAK tell whom and why it kills. Tested.

(Included in 2.4)

johnpol@2ka.mipt.ru: Re: Trivial patch for msbusmouse.c:
  > On Tue, Mar 19, 2002 at 03:22:58PM +1100, Rusty Russell wrote:
  > > Hi Russell,
  > >
  > > 	Please check this request_region() cleanup patch from Evgeniy
  > > Polyakov against 2.4 and 2.5.
  >
  > Both patches look fine, apart from the disgusting formatting being
  > different from the rest of the files.

  As you wish...

  > --
  > Russell King (rmk@arm.linux.org.uk)                The developer of
  > ARM Linux
  > http://www.arm.linux.org.uk/personal/aboutme.html


  	Evgeniy Polyakov ( s0mbre )

johnpol@2ka.mipt.ru: Re: Trivial patch for logibusmouse.c:
  > On Tue, Mar 19, 2002 at 03:22:58PM +1100, Rusty Russell wrote:
  > > Hi Russell,
  > >
  > > 	Please check this request_region() cleanup patch from Evgeniy
  > > Polyakov against 2.4 and 2.5.
  >
  > Both patches look fine, apart from the disgusting formatting being
  > different from the rest of the files.

  As you wish...

  > --
  > Russell King (rmk@arm.linux.org.uk)                The developer of
  > ARM Linux
  > http://www.arm.linux.org.uk/personal/aboutme.html


  	Evgeniy Polyakov ( s0mbre )

Rusty Russell <rusty@rustcorp.com.au>: 13) request_region check, 11-20:

Peter Chubb <peter@chubb.wattle.id.au>: make TAGS to work with bitkeeper:

  If you type, `make TAGS' in the top-level of a kernel tree that's been
  created with bk clone (or if you're using sccs to maintain your own
  copy), then the sccs control files are included in the TAGS file (sccs
  distinguishes its control files with an s. prefix rather than using a
  suffix, so the matches on '*.h' etc pick them up.)

Pavel Machek <pavel@ucw.cz>: typo in BK-usage.txt:

  Them them is not english...

Pavel Machek <pavel@ucw.cz>: Warn about ioctl collision:
  Hi!

  It is probably too late to fix it properly, but warning is better than
  nothing. (It confused the hell out of me...)
  									Pavel

Pavel Machek <pavel@ucw.cz>: Message changed in libc:
  Hi!

  ...so this change makes it way easier to grep...

  									Pavel

Paul Gortmaker <p_gortmaker@yahoo.com>: ENOTTY for rtc ioctl:
   ioctl(d, valid, crap) --> -EINVAL
   ioctl(d, crap, ....)  --> -ENOTTY

  man ioctl agrees:

         ENOTTY The specified request does not apply to the kind of
                object that the descriptor d references.

  Currently we return -EINVAL for both cases which is not as
  informative for debugging stuff.

  Patch is for 2.5.6 but applies cleanly (with minor offset) to 2.4.19p2

  Paul.

(Included in 2.2)
(Included in 2.4)

Paul Gortmaker <p_gortmaker@yahoo.com>: ENOTTY for nvram ioctl:
   ioctl(d, valid, crap) --> -EINVAL
   ioctl(d, crap, ....)  --> -ENOTTY

  man ioctl agrees:

         ENOTTY The specified request does not apply to the kind of
                object that the descriptor d references.

  Currently we return -EINVAL for both cases which is not as
  informative for debugging stuff.

  Patch is for 2.5.6 but applies cleanly (with minor offset) to 2.4.19p2

  Paul.

(Included in 2.2)
(Included in 2.4)

Martin Pool <mbp@samba.org>: trivial kernel patch -- clean up fs_exec.c:

(Included in 2.4)

Mark Hymers <markh@linuxfromscratch.org>: Kernel tree patch; Documentation_DocBook_kernel-hacking.tmpl:
  Hi,

  Just a small thing I noticed when grepping through the kernel source:
  one of the templates in Documentation/DocBook has a typo (I think).  I
  believe it should refer to MODULE_LICENSE instead of LICENCE.  Please
  correct me if I'm wrong though.

  Mark


(Included in 2.4)

Anton Blanchard <anton@au1.ibm.com>: newline in printk in olympic driver:

Christopher Yeoh <cyeoh@samba.org>: Re: fcntl returns wrong error code (Updated):
  At 2002/3/22 00:58+1100  Christopher Yeoh writes:
  > btw Stephen Rothwell pointed out that there is a much neater way to
  > achieve the same change. I'll post a new patch in the morning.

  This is the updated patch.


(Included in 2.4)

Andrey Panin <pazke@orbita1.ru>: serial.c ISAPNP fix:
  Thist patch fixes buglet which disables ISAPNP support in serial driver.
  __ISAPNP__ conditional symbol is used before isapnp.h is included.


(Included in 2.2)
(Included in 2.4)

Andrey Panin <pazke@orbita1.ru>: drivers_net_sis900.c: misiing __devinit:
  This patch adds missing __devinit modifier for read_eeprom() function.
  Patch against 2.5.8. Compiles, but untested.

Andrey Panin <pazke@orbita1.ru>: drivers_net_eepro100: missing __devinit:
  This patch adds missing __devinit modifiers for speedo_found1() and
  do_eeprom_cmd() functions. Patch against 2.5.8. Compiles, but untested.

Andrew Morton <akpm@zip.com.au>: fix a warning in i386_pci-pc.c:

Andrey Panin <pazke@orbita1.ru>: drivers_net_dl2k.c: missing __devinit's:
  This patch adds missing __devinit modifiers for read_eeprom() and
  parse_eeprom() functions. Patch against 2.5.8. Compiles, but untested.

 - sane retention policy for /proc/<pid>/fd/* - ->d_revalidate() says
   "kill it" if descriptor is not opened anymore (in addition to checks
   for task being dead) and we allow dentries of /proc/<pid>/fd/<n> to
   stay around.

 - preparation for sane policy for /proc/<pid>/fd/* - don't store
   struct file * in these inodes anymore.

 - sane dentry retention.  Namely, we don't kill /proc/<pid> dentries at the
   first opportunity (as the current tree does).  Instead we do the following:
	* ->d_delete() kills it only if process is already dead.
	* all ->lookup() in proc/base.c end with checking if process is still
	  alive and unhash if it isn't.
	* proc_pid_lookup() (lookup for /proc/<pid>) caches reference to dentry
	  in task_struct.  It's _not_ counted in ->d_count.
	* ->d_iput() resets said reference to NULL.
	* release_task() (burying a zombie) checks if there is a cached
	  reference and if there is - shrinks the subtree.
	* tasklist_lock is used for exclusion.
   That way we are guaranteed that after release_task() all dentries in
   /proc/<pid> will go away as soon as possible; OTOH, before release_task()
   we have normal retention policy - they go away under memory pressure with
   the same rules as for dentries on any other fs.

 - new helper in fs/proc/base.c - name_to_int(dentry) returns ~0U if name
   doesn't match 0|[1-9][0-9]* or is too large.  Otherwise it returns
   numeric value of name.  proc_pid_lookup() and proc_lookupfd() converted.

 - take unhash_process() into sched.c, move zeroing ->pid into it (and
   under tasklist_lock)

Fix buffer-head leak on truncate race.

The reason why it hadn't been triggered left right and center is that we
step on that path only when partial truncate blows away an indirect
block shared between truncated and remaining areas _and_ races with
ext2_get_block() in the beginning of said area.  IOW, we need

	* indirect block with hole in the beginning
	* get_block starting to read that block
	* truncate killing everything past the hole (and thus freeing indirect
	  block in question)
	* get_block completing the read and noticing that block is actually
	  gone.

OK...  IMO we should do that brelse() outside of the loop.

 - fixed off-by-PAGE_OFFSET in populate_pmd() (alpha, again)

 - alpha/mm/init.c forgot to set max_pfn

 - (dumb) default_idle() provided (alpha)