- Export ip_generic_getfrag
- In udp6 increment v6 udp statistics not v4 one

* packet type converted from linked list to list_macro
* writer lock replaced with spin lock, readers use RCU
* add __dev_remove_pack for callers that cant sleep.
* af_packet changes to handle and sleeping requirements, and possible
  races that could cause.

into nuts.ninka.net:/home/davem/src/BK/net-2.5

This makes sure that the ioperm bitmap in the TSS is correctly set up
during the first ioperm() call.  Without this the TSS bitmap contains
random garbage until the next context switch.

Initializers must be constant expressions, and thus we can't use the
complex expression "cpu_to_le*()" - the end result of which may have a
constant _value_ but the expression itself isn't a constant expression.

So use the explicitly constant "__constant_cpu_to_*()" expression
instead.

This fixes a typo reported by Geert, and more significantly
fixes static linking so that it works even when only the
device side of USB is enabled, and the host side (CONFIG_USB)
isn't.

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

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

We'll do it *after* IDE taskfile IO is done
Cset exclude: axboe@suse.de|ChangeSet|20030511184946|49736

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

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

Alan and I were investigating this, but we don't know why the problem
occurs.

This reverts the previous handling of masked_irq, and fixes the problem.

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

This changes apm.c to invoke suspend.c's save and restore processor
state procedures around suspends, which fixes the SYSENTER MSR problem.

The patch also decouples sysenter.c from SOFTWARE_SUSPEND: the variables
used (only!) in suspend_asm.S are moved there, and the include file now
declares the procedures called from apm.c (previously they were only
called from suspend_asm.S).

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

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

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

Kudos to Wayne Scott @ BitMover for this.

this patch has been sleeping
in Alan tree for quite some time. It updates the depca driver to the
EISA/sysfs API, gets rid of check_region, and properly reserve memory
region. Patch is against latest BK.

it turns out the tulip driver is a much better driver for the integrated
ali1563 ethernet than the dmfe driver... the dmfe driver gets tx timeouts
every ~15s and can't receive over 5MB/s.  but with the small tulip patch
below i'm seeing 11MB/s+ in both directions without problems.

This patch updates the bmac and mace ethernet drivers so that their
interrupt routines return an irqreturn_t, and updates the bmac driver
to use a spinlock rather than global cli/sti.

        This patch update the Wavelan Pcmcia driver for Wireless
Extensions 16, and also remove all the backward compatibility cruft
that is broken anyway.

        This update the Wavelan ISA driver for Wireless Extension 16
(going with my previous patch).

        This patch for 2.5.68-bk11 will update Wireless Extension to
version 16 :
        o increase bitrate and frequency number for 802.11g/802.11a
        o enhanced iwspy support
        o minor tweaks and cleanups

        This patch is only for the core of WE. The patches for the
individual drivers have been sent to their respective maintainers.
	Compared to the previous version I sent you a few weeks ago,
I've just updated to the latest kernel.

        This patch for 2.5.68-bk11 will fix the irq handler of some
obsolete wireless drivers (wavelan, wavelan_cs and netwave_cs) plus
assorted fixes. All those drivers have been tested on a SMP box.

This cleans up the driver big time and gets rid of a big ugly wart
in setup.c.  Note that I don't have the hardware so this is only
compile-tested.

This patch adds dynamic allocation of request structures. Right now we
are reserving 256 requests per initialized queue, which adds up to quite
a lot of memory for even a modest number of queues. For the quoted 4000
disk systems, it's a disaster.

Instead, we mempool 4 requests per queue and put an upper limit on the
number of requests that we will put in-flight as well. I've kept the 128
read/write max in-flight limit for now. It is trivial to experiement
with larger queue sizes now, but I want to change one thing at the time
(the truncate scenario doesn't look all that good with a huge number of
requests, for instance).

Patch has been in -mm for a while, I'm running it here against stock 2.5
as well. Additionally, it actually kills quite a bit of code as well