* Add TSO get/set command to ethtool interface.  Applies to both 2.4/2.5.
  Ethtool application patch sent under separate cover.

ne2k-pci leaks memory on unload. dev->priv is allocated in ethdev_init(), but
never freed. against 2.4-bk, but also applies to 2.5-bk with offset.

into redhat.com:/garz/repo/net-drivers-2.6

Previous entry said to be out of date by two years or more.

As noted by Gergely Nagy:

  "devfs_mk_cdev() first checks the mode passed to it, and if it thinks
   it is not a char device, it prints a warning and aborts.  Now, this
   printing involves the local variable `buf' (char buf[64]), which is
   not initialised at that point."

The same problem also affects devfs_mk_bdev.

Fixed thus.

davidm@hpl.hp.com writes:
  "I'm working on updating the ia64 tree with local_t etc.  One
   thing that would really help me: could you make
   asm-generic/percpu_modcopy() a macro?  The routine depends on
   cpu_possible(), but I can't including smp.h in percpu.h since
   that would lead to recusive header-file dependencies (and in my
   opinion, percpu.h should be more "primitive" than smp.h, so that
   it can be included virtually everywhere)."

A few places pre-declare "int module_init(void);" and "void
module_cleanup(void);".  Other than being obsolete, this is
unneccessary (it's in init.h anyway).

There are still about 100 places which still use the
obsolete-since-2.2 "a function named module_init() magically gets
called": this change frees us up implement that via a macro.

Author: Neil Brown

Define module_put_and_exit() and use it for nfsd/lockd

Both nfsd and lockd have threads which expect to hold a reference
to the module while the thread is running.  In order for the thread
to be able to put_module() the module before exiting, the
put_module code must be call from outside the module.

This patch provides module_put_and_exit in non-modular code which a
thread-in-a-module can call.  It also gets nfsd and lockd to use it
as appropriate.

Note that in lockd, we can __get_module in the thread itself as the
creator of the thread is waiting for the thread to startup.

In nfsd and for the 'reclaimer' threaded started by locked, we
__get_module first and put_module if the thread failed to start.

Somehow, the code which taints the kernel when rmmod -f is used got
lost.  Restore it.

These are the local_t bits for sparc64.

Other platforms such as PPC64 and Alpha (and in fact any "load locked/
store conditional" like platform other than IA64), probably want to do
something similar.

Uses local_t for module reference counts.

Introduces local_t, a type which is like atomic_t, but the
operations are only atomic from a single CPU's point of view
(ie. atomic against interrupts and softirqs). Some architectures
(eg. i386) can implement these very efficiently.

There are special operations for the case of a local operation on a
per-cpu variable (which is common), which some architectures can
implement efficiently (eg. IA64 keeps all per-cpu variables mapped
at the same address, so no address arithmetic is needed).

The generic implementation given here simply uses atomics on 32-bit
archs, three variables on others.  x86 is already implemented specially.

Richard Henderson point out a while back that linker generated symbols
should be declared as: "char _text[]" so that the compiler can't make
assumptions about them sitting in small sections, etc.

Centralize these defintions in asm/sections.h (where some already
are on x86).

The current percpu macros do not allow __get_cpu_var(foo.val1)
which makes building macros on top of them really difficult.  The
reason for this is the __per_cpu postfix appended to per-cpu
variables, designed to catch direct uses.  Prepend it instead.

tests.

From Dennis Vshivkov: 

  "whenever I was trying to create a file using only national
   characters for its name, it was always created with an
   uppercased shortname (provided that the name was not too
   long for 8.3, of course). Everything was fine with latin
   filenames, though."

The bug is that we check "buf[0]" as an unsigned character, but
"buf" is just "char *", which (depending on architecture and
compiler options) tends to be signed.

The joys of having several arches at my home lab, thanks
to parisc this time.

Adds kahlua, harmony and hal2 drivers to the build options.

Fix an assortment of unchecked copy_to_user().

Memory leak fix: hw_config is allocated before the call to sb_dsp_detect.

into home.osdl.org:/home/torvalds/v2.5/linux

into jet.(none):/home1/jejb/BK/scsi-for-linus-2.5

This allows the low-level start code to be located far away from the
rest of the kernel, which is sometimes necessary.

This feature is not actually MA1-specific, so get rid of the `MA1' in
the name.

Some updated copyright noticed and an unnecessary variable deleted.

This updates the v850 Kconfig and kernel/Makefile to reflect preceding
changes.

This patch adds support for the `sim85e2s' simulation of the NA85E2S
processor implementation.  As part of this, cache-flushing support for
the common v850e2 cache implementation is added.

It also cleans up a bunch of code that was duplicated between different
v850e2 processors.

This adds a port to the V850E/ME2 processor, and the `SolutionGear mini'
RTE-V850E/ME2-CB evaluation board.

This allows ports that support the v850 RTE-CB `GBUS' interrupts to use
both them and processor-board-specific interrupts at the same time.

(1) Add support for the V850E/ME2 processor

(2) Clean up the cache-flushing function naming a bit

(3) Similar to previous patches, rename everything from `nb85e' to `v850e'.
    This patch renames some files, and so contains a number of whole-file
    add/removes.

The v850 family contains several related-but-not-identical on-chip
UARTs.  This patch factors out the common code and uses it to implement
both types (only one was supported before).

Also, this patch changes the way the v850 UART is initialized, to use
the same method as other linux serial drivers.

This patch renames the UART code to be `v850e_uart' rather than
`nb85e_uart', as the former is more correct.  As this change renames
some files too, the patch contains a number of whole-file add/removes.

The term `nb85e' is incorrect (caused by my confusion when starting the
v850 port), so this renames all occurances to `v850e'.

Because this change renames some files too, it contains a number of
whole-file add/removes.