... is finally done.

Trivial patch update against 2.5.17:
johnpol@2ka.mipt.ru: 23) request_region check, 21-30:
  here is one more trivial check.

  So please test and apply.

  	Evgeniy Polyakov ( s0mbre )

Trivial patch update against 2.5.17:
johnpol@2ka.mipt.ru: Re: 47) request_region check, 41-50:

Trivial patch update against 2.5.17:
johnpol@2ka.mipt.ru: 21) request_region check, 21-30:
  here is one more trivial check.

  So please test and apply.

  	Evgeniy Polyakov ( s0mbre )

johnpol@2ka.mipt.ru: 18) request_region check, 11-20:
  here is one more trivial check.

  So please test and apply.

  	Evgeniy Polyakov ( s0mbre )

(Included in 2.4)
johnpol@2ka.mipt.ru: 1) request_region:
  > 	Send them one at a time.  Last time I had to write a script to
  > mail them one at a time to myself.

  Ooops, sorry... I've got a gluk...

  > Thanks!
  > Rusty.
  > --
  >   Anyone who quotes me in their sig is an idiot. -- Rusty Russell.


  	Evgeniy Polyakov ( s0mbre )

Trivial patch update against 2.5.17:
Tim Schmielau <tim@physik3.uni-rostock.de>: move jiffies from sched.h to it's own jiffies.h:
  Move 'jiffies' from sched.h to their own header.
  Then pull the sched.h dependency from 67 files that include sched.h for
  no apparent reason other than the jiffies declaration.

  Move the time_[before,after}{_eq}() macros from timer.h to jiffies.h,
  since there are *no* files using them that don't also use jiffies.

  Many more sched.h dependencies can be killed after capable(),
  request_irq(), and free_irq() are moved out of <linux/sched.h>.


  Tim Schmielau <tim@physik3.uni-rostock.de>

Trivial patch update against 2.5.17:
dipankar@in.ibm.com: smp_call_function change:
  My earlier patch fixed only i386. As per Dave Miller's suggestion,
  I have fixed smp_call_function for other smp architectures too.

  Description
  -----------
  Going by the documentation and use of _bh version of spin_lock(),
  smp_call_function() is allowed to be called from BH context,
  We can run into a deadlock with some locks if we do so.
  This because reader-writer locks can sometimes be used optimally
  by not disabling irqs while taking the reader side if only the
  reader side of the lock is taken from irq context.

        CPU #0                                CPU #1

        read_lock(&tasklist_lock)
                                         write_lock_irq(&tasklist_lock)
                                         [spins with interrupt disabled]
        [Interrupted by BH]
        smp_call_function() for BH
             handler
                                         [ doesn't take the IPI]

  So, cpu #1 doesn't take the IPI and cpu #0 spinwaits
  for the IPI handler to start, resulting in a deadlock.

  The last time I looked, I couldn't see smp_call_function() being
  called from BH context anywhere. So, there is no immediate problem.
  However it seems right to correct the documentation and also not
  disable BH while taking the call lock since it isn't necessary.
  This patch does exactly that.

  Thanks
  --
  Dipankar Sarma  <dipankar@in.ibm.com> http://lse.sourceforge.net
  Linux Technology Center, IBM Software Lab, Bangalore, India.

  smp_call_func-2.5.14-1.patch
  ----------------------------

(Included in 2.4)

Stephen Rothwell <sfr@canb.auug.org.au>: small typo in signal code for cris, mips and mips64:
  Hi Linus,

  This looks very obvious to me but I may be mistaken.

  I haven't even attempted to build this as I don't have machines
  of any of the affected archs.

  --
  Cheers,
  Stephen Rothwell                    sfr@canb.auug.org.au
  http://www.canb.auug.org.au/~sfr/

(It's ttyS in every other message in the driver).

Zwane Mwaikambo <zwane@linux.realnet.co.sz>: serial unload message:

Stephen Rothwell <sfr@canb.auug.org.au>: small typo in signal code for cris, mips and mips64:
  Hi Linus,

  This looks very obvious to me but I may be mistaken.

  I haven't even attempted to build this as I don't have machines
  of any of the affected archs.


(Included in 2.4)

Stephen Rothwell <sfr@canb.auug.org.au>: fix for sigio delivery:
  Hi Linus,

  This patch means that we keep the upper 16 bits of the si_code
  field of the siginfo structure that is delivered with and SIGIOs.
  We need this so that the code that actually copies the siginfo_t
  out to user mode knows which part of the union to copy.  We currently
  get away with out this information because we always copy at least
  two ints worth of the union, but this s an ugly hack and I would
  like to tidy it up.

  Comments?

Rusty Russell <rusty@rustcorp.com.au>: Trivial patch to remove minmax macros:
  Hi Harald,
  	The MIN & MAX etc. macros aren't used anywhere, and kernel.h
  has the new min & max anyway, which should be used.

  Cheers,
  Rusty.

(Once again, Ralf said straight to you).

Rusty Russell <rusty@rustcorp.com.au>: Trivial MIPS gt64120-pci patch to remove minmax macros:
  Also changes over to standard ALIGN macro:

(Ralf said to send this straight to you)

Rusty Russell <rusty@rustcorp.com.au>: Trivial MIPS baget patch to remove minmax macros:
  In favour of kernel.h one:

Roger Luethi <rl@hellgate.ch>: DMA-mapping.txt: sg_dma_length() -> sg_dma_len():

[UTS_MACHINE is now defined in the (generated) compile.h]

David Gibson <david@gibson.dropbear.id.au>: [TRIVIAL PATCH] Fix order of #includes in init_version.c:
  Linus, please apply.  compile.h must be #included before uts.h, or
  uts.h will define UTS_MACHINE (incorrectly) which is then redefined in
  compile.h.

David Gibson <david@gibson.dropbear.id.au>: TRIVIAL: Remove warning in fs_nfs_nfsroot.c:
  Linus, please apply.  The patch below removes a warning in
  fs/nfs/nfsroot.c by including a header file providing a prototype for
  in_aton().

Andrey Panin <pazke@orbita1.ru>: printk() cleanup in ide-pnp.c:
  Attached patch adds a few missing printk levels in ide-pnp.c file.

Andrey Panin <pazke@orbita1.ru>: drivers_net_sundance.c: missing __devinit:
  this patch adds missing __devinit modifier to sundance.c network driver.
  Patch against 2.5.15. Compiles, but untested.

"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>: [patch] 2.4.19-pre7: A few declance multicast updates:
  Hello,

   It seems all Ethernet device drivers were bulk-converted to use the new
  common CRC functions.  I discovered declance used incorrect endianness to
  calculate the sum for its multicast filter and had a few alignment
  problems there.  I fixed these bugs in the MIPS/Linux CVS tree which is at
  2.4.18 now.  Here is the respective update for the official kernel.

   The bugs make the filter non-functional.  Please apply.

    Maciej

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

	nfsd_acceptable() calls permission() on a a dentry that is
not guaranteed to stay around (its child is pinned down, but there
is no promises that child won't move and nothing pins dentry itself).
Fixed, cleaned up.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

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

Use the just introduced Rules.make extension to clean up 
drivers/net/*/Makefile.

New-style Makefiles have a nice way of declaring objects
which need to be built either built-in or as modules:

        obj-$(CONFIG_EEPRO100) += eepro100.o

However, handling objects in subdirectories, which need to be
built and linked is not as nice:

        subdir-$(CONFIG_E100) += e100

        ifeq ($(CONFIG_E100),y)
          obj-y += e100/built-in.o
        endif

This means we descend into the subdirectory when building
vmlinux / modules, depending on CONFIG_XXX. When we are building
vmlinux we also need to link whatever has been built in the
subdirectory, so we add it to $(obj-y) at the appropriate place
(link order is important).

Now, the extension below allows to rewrite the second case into

         obj-$(CONFIG_E100) += e100/

which looks much nicer ;-) Existing behavior is not changed, and the
only prerequisite to using the extension above is that the O_TARGET in
the subdir is named "built-in.o".

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

Currently fs.h is full of unrelated declarations and included in almost
any source file. Thus it makes sense to spilt certain aspects out that are
only used by few users.

This patch starts with the namei/path lookup interface and splits it into
<linux/namei.h> which is now directly included by the 24 files that actually
need it.

Transform new quota code to use sysctl instead of /proc/fs.

	default encode_fh() doesn't take dparent_lock around messing
with dereferences of ->d_parent->d_inode->i_....  Fixed.

	OK, it turned out that since the last time I've done that audit
a couple new users of d_parent had appeared.  First, more crapectomy (strictly
speaking not necessary, but just look at that code - where the hell does IBM
find them?)

 - Apply small host chip driver cosmetics by Andrej xxx Panin
   and Vojtech Pavlik.

 - Remove support for "disc recovery time". It could only supposedly
   help with really simplistic broken devices from the past,
   which didn't have moderately sophisticated controllers.
   And finally Vojtech voted for it as well... so I just trust him.

 - Apply icside host chip driver and other ARM related updates by Russell King,
   which finally settle the "portability" work a bit, well hopefully.

 - Make the different ATAPI device type drivers use a unified packet command
   structure. We have to start to push them together.

This patch is rather trivial in itself, but the plentora of code duplication it
is trying to fight against is making it unfortunately rather big...

 - Nuke COMMERIAL and similar spurious configuration options...
   The fact that every single default configuration option contained
   those bits makes this trivial patch appear rather big.

 - Move ll_10byte_cmd_build to the only place where it's used: ide-cd.  The SCSI
   layer does have it's own implementation which additionally it's messing
   around with the hard_nr_sectors struct request value.  One should *not*
   provide "infrastructure" until its really used as such.

   If anywhere this should reside in a file called ATAPI.

 - Unfold the INIT_REQUEST macro from blk.h. This showed up plenty of duplicate
   checks for QUEUE_EMPTY. Clean them as well. Remove the over cautious
   major(CURRENT->rq_dev != MAJOR_NR) checks. During the last several years I
   never saw any report about it. Looking at the !CURRENT->bio it is clear that
   dereferencing NULL will provide the same kind of panic as the check.  Some
   comments around the code in question show nicely that indeed INIT_REQUEST
   was a good example of code obfuscation.

 - A short look at RQ_INACTIVE shows that it is only used inside the scsi.c file
   and during the removal of devices. This shows that the many checks for
   RQ_INACTIVE are not necessary. Looking closer even shows that some of them
   did happen before checks for an empty queue. Plenty of drivers didn't care
   about it and the CD-ROM ones should be handled properly, because the
   most common drivers would fail as well. Comments indicate that this
   was an leftover from 1.3 days...

 - Apply cleanup of host chip drivers by Bartomiej Zonierkiewicz:

     affected drivers - aec62xx.c, alim15x3.c, cmd64x.c, hpt34x.c, sis5513.c

     new tuning scheme (wip) part 1:
	- introduce ratemask()
	- use ata_timing_mode()
	- use ide_config_drive_speed() return value

     forward port from convert.10:
	- support for AEC6280, AEC6280R
	- misc cleanups

     I had to fix a small typo in sis5513 code...

 - Add a new entry for an old VIA cell hiding as something new.
   (Pointed out by Kees Bakker.)

 - Make the synchronization token active resident on the same level as the
   spin lock. They interact with each other.

 - Synchronize with linux-2.5.17.

 - HPT366 driver typo fix by Andries Brouwer.

 - Export udma_tcq_enable() symbol right now. The blk_get_request() is undefined
   as well.

	Unlike other drivers, rd.c wants block size to be set once an
forever (for everybody else setting block size as high as possible and
letting filesystems change it with set_blocksize() is OK; rd.c treats
invalidate_buffers() as "kill the ramdisk contents".