The current top-level Makefile has a fundamental problem which
makes "make oldconfig vmlinux" impossible:

It includes .config, which is changed by "oldconfig". So after "oldconfig"
.config has changed and the .config the Makefile had read is obsolete.
make provides a mechanism to cope with this, it'll restart automatically 
if any of the files it included changed, if you let it know that you
changed it, just using a normal rule which has .config as its target.

However, once you tell make that "make oldconfig" changes .config, you
have another problem: oldconfig always uses .config to be remade, there's
no mechanism to tell if it's up to date. So makes notices that .config
has changed, restarts, makes oldconfig again, notices that .config has
changed, restarts, ... you get the picture.

The way to solve this is to do a proper two-stage approach: If you just
say "make oldconfig", there's no need for the Makefile to even read the
.config. If it does not, it won't restart and recurse infintely.
So we divide the Makefile into two sections: One for targets which don't
need the variables from .config, like *config, clean, mrproper and
one section which does the actual build, which needs to know the
CONFIG_ options.

If one of the "noconfig" targets is given, we handle those, without
reading .config. From there, we call make again, filtering out the already
handled targets, to do the main work.

The fact that this actually works correctly can be seen by trying
"make vmlinux oldconfig" which will execute things in the right
order - and this is not just nitpicking, it means that "-j" will
get this case right, too.

The $(CONFIGURATION) hack used to start "make config" automatically
can go away now, too. Since we don't know which of make *config the
user prefers, we'll just ask him call "make whatever-config" himself,
instead of forcing "make config" on him.

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

Same thing as patch #1165/1 but for 2.5.x

The kernel expects these to return values in unsigned long types.

- remove LAST_DESC in favour of passing the array size to iotable_init
- replace domain and permission bits/cache attributes with a generic
  "type", which can be easily converted to the required domain and
  permission bits/cache attributes at run time.  It also removes the
  possibility for getting such things wrong and (accidentally)
  allowing all user space to fiddle with devices directly.

This patch removes fsuser().  Now both suser() and fsuser() are gone and
all permission checks use an appropriate capable() call.

Attached patch replaces the lone remaining suser() call with capable()
and then removes suser() itself in a triumphant celebration of the glory
of capable().  Or something. ;-)

Small cleanup of capable() and some comments, too.

 - Simplify ide_cmd_type_parse by removing the handling of commands which we
   never use.

 - Realize that pre_task_out_intr and pre_task_mulout_intr are semanticaly
   identical. Use only pre_task_out_intr(). This allowed us to
   eliminate the prehandler altogether.

 - Updated fix for misconfigured host chips by Vojtech Pavlik.

 - Be more permissive about ioctl handling to allow device type drivers to do
   they own checks.

 - ali14xx cleanups by Andrej Panin.

 - Unfold usage ide_cmd_type_parser in tcq.c code. This makes this operation
   local to ide-disk.c. Move it as well as the interrupt handlers used only for
   the handling of disk requests there too.

 - Guard against calling handler before the drive is ready for it in
   ata_taskfile()! Well this bug was there before, but right now we inform
   about it.

 - Unfold ide_cmd_type_praser in ide-disk.c. Merge the remaining bits of it with
   get_command. Well it's no more.

 - Move recal_intr to ide.c - the only place where it's used.

This doesn't change the "mechanics" of the code but it makes it a lot more
"obvious" what's going on.

2.5.20 seems to be incapable of executing binaries in a ramdisk-based
root filesystem.  The ramdisk in question is an ext2fs, with a 1K
block size loaded via the compressed ramdisk loader in do_mounts().

It appears that, in the case of a 1K block sized filesystem, we attempt
to read two 512-byte sectors into a BIO vector.  The first one is copied
into the first 512 bytes.  The second sector, however, is copied over
the first 512 bytes.  Obviously not what we really want.

Rev. 2, slightly cleaned up:

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

Noted by Alexey Vyskubov

- Make sure proper pci id is passed to probe()
- make sure pci_dev->driver is set and reset on driver registration/unregistration
- call remove_driver to force unload of driver on unregistration

driver_unbind was called when drv->refcount == 0.
It would call driver_for_each_dev to do the unbinding
The first thing that would do was get_device, which...
BUG()'d if drv->refcount == 0. 
Duh. 

- make sure drv->devices is initialized on registration (from Peter Osterlund)
- add remove_driver for forcing removal of driver

There was a potential race with the module unload code. When a pci driver was unloaded, it would call pci_unregister_driver, which would simply call put_driver.
If the driver's refcount wasn't 0, it wouldn't unbind it from devices, but the module unload would still continue. 
If something tried to access the driver later (since everyone thinks its still there), Bad Things would happen. 
This fixes it until there can be tighter integration between the device model and module unload code.

Here's followup patch that makes it work. Notice freeze_processes() --
if you don't do that you risk data corruption.

This cleans up swsusp in 2.5.20. Killed sysrq-D support (it is too
much trouble to support suspending from interrupt), kill unused
define, fix compile-time warnings (thanks to Adam).

I created arch/i386/suspend.c not to clash with ACPI people so much in
future. (More stuff is going to move into it in the future, to clean
up functions that really do not belong to the headers.)

This patch merges in all the currently outstanding bluesmoke bits from
2.5-dj to 2.5.20, it also has the pleasant side effect of fixing the
compilation. Test compiled with and without MCE.

  Here's that patch again (MIME this time, so tabs don't get
  lost by my silly gui mailer); applies cleanly against against 2.4.19-pre8.
  Nobody commented on it last time I posted it, and it does
  make compiling gcc easier, so I guess that makes it trivial patch
  monkey fodder.  Or am I making a silly mistake?

  Most /proc/slabinfo cache_names are in the format:
  cache_name.  There are a couple with spaces in the
  name, which is inconsistent and requires a special case
  when scripting.

  Changes "fasync cache" and "file lock cache" to have
  the usual underscore.

  inactive_list and active_list are global, yet they are repeatedly
  initialized using INIT_LIST_HEAD() in free_area_init_core(). This
  patch is originally due to Christoph Hellwig, and by some reports
  has been implementated before in 2.4-based trees by Andrea Arcangeli.

  The memlist_* macros serve as nothing but an insulation layer from the
  Linux-native generic list operations. This patch removes them in favor
  of using generic list operations directly.

  This comment, describing how to optimize for gcc-2.2.2, is so outdated
  it should be removed. It's also quite doubtful it should ever have been
  placed in this file at all (perhaps something under Documentation/ ?).
  This patch removes it.

  memclass is too large to be a #define; it overflows 80 columns and does
  not make use of facilities available only to macros.

  This patch convert memclass() to be an inline function.

  I found this one while trying to straighten out bootstrap ordering
  issues elsewhere.

  There appears to be a duplicate declaration of rq in sched_init().
  This removes the nested declaration and otherwise leaves things alone.

  The comment describing the usage of zone_table[] assumes the existence
  of an unsigned char page->zone field from the original implementation
  of page->zone size reduction. This patch corrects the comment to
  accurately describe the lookup mechanism used by page_zone() and also
  to mention explicitly the sole user of the table, page_zone().

Playing with arch stuff does this to you.

Rusty Russell <rusty@rustcorp.com.au>: Oh, I feel so violated...:
  <sniff>

  This patch against 2.5.19 gets rid of some bogus casts in ide-cd.c
  In my opinion the casts as is are bugs waiting to happen.

  I found that 'max' pointer is not updated in proc_dointvec_minmax()
  and proc_doulongvec_minmax(), when I write smaller values than min to
  /proc/sys entry (and val<*min++ check becomes true.)
  This may lead to min/max checking of values with bogus maximum.

  Unrelated to my first dcache patch, this is something more crucial
  and should be applied first.

  fs/dcache.c:
   - handle d_alloc() returning NULL.

  Attached is a really trivial patch that changes an "unknown" PCI_DEVICE_ID
  0x3112 to PCI_DEVICE_ID_VIA_8361 in drivers/pci/quirks.c .

  It applies cleanly to 2.5.18 and 2.4.19-pre8.

  There is more of this janitorial work to come (eg General setup). I'm just
  piecemealing it

  [ Made applicable with -p1 by Rusty ]

  nlma fixes a call to netlink_broadcast with GFP_KERNEL ( passed to
  skb_clone ) while we are in_interrupt() ( catched by a BUG() in
  slab.c:1109 ).

  Missing include of asm_io.h in mm_bootmem.c:
  Submitted this trivial patch on May 14, but nothing has happened yet.
  Perhaps better chance if you took care of it.

  It's needed by phys_to_virt() but it happens to work on i386 etc.
  since dma.h includes io.h for that arch.

The following has been vetted with davem w.r.t. the change to
KM_SKB_DATA. Apologies for the bug...

include/asm-*/kmap_types.h:
   Replace the unused km_type slot KM_SKB_DATA with
   KM_SKB_SUNRPC_DATA.

net/sunrpc/xdr.c:
   Replace the use of KM_USER0 with KM_SKB_SUNRPC_DATA for copying
   data from an skb into the page cache when in the sk->data_ready()
   callback.

Fix queue plug locking.

This fixes two shift warnings on 64 bit archs.

  oom-loop fixes error handling after a netlink failure - it does not do a
  cleanup and it makes every next call to ip_fw_check to detect a
  loop and drop the packet.