From:  Arnd Bergmann <arnd@bergmann-dalldorf.de>

  The function init_irq is only used in ide-probe.c, so it should
  better be static.

From:  Arnd Bergmann <arnd@bergmann-dalldorf.de>

  balloc[] and tails[] are used only in the file they are defined
  in, so they should be made static

From:  Arnd Bergmann <arnd@bergmann-dalldorf.de>

  The strdup function in sunrpc should not be global

From:  Arnd Bergmann <arnd@bergmann-dalldorf.de>

  Variables named 'io' and 'dma' should not be global

From:  Arnd Bergmann <arnd@bergmann-dalldorf.de>

  A global variable should not be called 'verbose'. It can
  be made static since it is only used in one file.

From:  Bob Miller <rem@osdl.org>

  Deleted an unused stack variable from sc1200_suspend.

From:  Pablo Menichini <pablo@menichini.com.ar>

From:  Pablo Menichini <pablo@menichini.com.ar>

From:  william stinson <wstinson@wanadoo.fr>

  this proposed patch for drivers/scsi/cpqfcTSinit.c scsi driver for
  Linux removes two calls to check_region using request_region instead

  This is patch number 28 in a series of check_region patches I am doing as
  part of the kernel janitors project.

From: Rusty Lynch <rusty@stinkycat.com>

  VT support requires drivers/char/keyboard.c which makes function
  calls implemented in drivers/input/, so that attempting to set
  CONFIG_INPUT=m or just not setting CONFIG_INPUT will result in a
  compile error if CONFIG_VT is on.

From:  william stinson <wstinson@wanadoo.fr>

  this patch for drivers/ide/legacy/umc8672.c ide driver for Linux
  removes one call to check_region using request_region instead

  I don't have this hardware so patch is not tested.  This patch removes
  all references to check_region in this driver.

  This is patch number 31 in a series of check_region patches I am doing as
   part of the kernel janitors project.

From:  Arnd Bergmann <arnd@bergmann-dalldorf.de>

  The pas2 driver has a global variable named 'lock', which
  pollutes the global namespace. This patch adds a pas_
  prefix. The same is done for 'translate_code'.

From:  Arnd Bergmann <arnd@bergmann-dalldorf.de>

  The i8k driver has global variables named 'force' and 'power_status'
  that pollute the name space. This makes them static.

From:  Geert Uytterhoeven <geert@linux-m68k.org>

  Kill duplicate extern char _stext (already declared globally 14 lines before)

From:  Chris Wilson <chris@qwirx.com>

  As part of the Linux Kernel Janitors project, I would like to submit my
  patch for bpqether.c.

  The document Documentation/cli-sti-removal.txt says that cli() should no
  longer be used to disable interrupts. This patch removes all references to
  cli() and {save,restore}_flags.

  - added a static spinlock to protect bpq_devices
  - changed cli/sti and {save,restore}_flags to taking the spinlock and
    disabling interrupts with spin_lock_irqsave
  - included my previous patch for proc_net_create, but as a separate hunk,
    so if you've already applied then just ignore the rejected hunk.

  I have verified that the patched driver compiles without warnings, but
  since I don't have the hardware I can't test it. Please treat with
  caution.

From:  william stinson <wstinson@wanadoo.fr>

  this proposed patch for drivers/atm/ambassador.c atm driver for Linux
  removes one call to check_region using request_region instead

  I don't have this hardware so patch is not tested.  This patch removes
  all references to check_region in this driver.

  This is patch number 30 in a series of check_region patches I am doing as
   part of the kernel janitors project.

From:  Bob Miller <rem@osdl.org>

  The function, cs5520_tune_chipset() is declared to return an int.
  Added a return statement instead of just falling of off the bottom.

From:  Arnd Bergmann <arnd@bergmann-dalldorf.de>

  A global variable should not be called 'debuglevel'. It can
  be made static since it is only used in one file.

From:  Arnd Bergmann <arnd@bergmann-dalldorf.de>

  A global variable should not be called 'ioctl_mutex',
  this makes it static.

The address allows oprofile and ksymoops to work again.  The state is
simply informative.

From:  Marcus Alanen <maalanen@ra.abo.fi>

  Moves the snd_legacy_find_free_ioport definition to opti92x-ad1848.c,
  since it is the only user.

From:  Arnd Bergmann <arnd@bergmann-dalldorf.de>

  The skfp driver has a global function named 'set_int'. This makes
  it static to avoid namespace pollution.

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

into raven.il.steeleye.com:/home/jejb/BK/scsi-for-linus-2.5

The below does two things:
(i) do not try to spin up a CF reader without media
(ii) be careful when asking for the cache parameters mode page

[do not ask for this page when no media are present:
it is meaningless, and some devices react badly if we do;
check the reply so that we do not read past the end of the reply;
first give a small transport length - some USB devices are unhappy
if we ask for more than they provide]

Andries

This cleans up the delay code by moving the timer-specific
implementations into the timer_ops struct.  Thus, rather then doing:

	if(x86_delay_tsc)
		__rdtsc_delay(loops);
	else if(x86_delay_cyclone)
		__cyclone_delay(loops);
	else if(whatever....

we just simply do:

	timer->delay(loops);

Making it much easier to accommodate alternate time sources.

This creates an empty timer_opt structure (timer_none) which is then
used as a default initializer to the timer pointer.  This lets us avoid
having to check before dereferencing the timer in future code.

This patch moves BUG() and PAGE_BUG() from asm/page.h into asm/bug.h.

We also fix up linux/dcache.h, which included asm/page.h for the sole
purpose of getting the BUG() definition.

Since linux/kernel.h and linux/smp.h make use of BUG(), asm/bug.h is
included there as well.

In addition, linux/jbd.h did not contain a clear path with which to
obtain the archtecture BUG() definition, but did contain its own
definition.

The following patch adds an explicit no list of arches who do not want
to have the "Enhanced Real Time Clock Support" RTC driver asked.  This
adds PPC32 (who for a long time had their own 'generic' RTC driver, and
then have adopted the genrtc driver) and PARISC (who have always used
the genrtc driver).  Per request of Peter Chubb, IA64 is on this list as
well.

The problem is that on some archs there is no hope of this driver
working, and having it compiled into the kernel can cause many different
problems.  On the other hand, there are some arches for whom that driver
does work, on some platforms.  So having an explicit yes list would
result in some rather ugly statements.

This fixes the wrong order of array(amd_ide_chips) that causes a BUG()
in 436 line with any conditions, because we use the wrong amd_config.

This is needed to compile kernel/cpufreq.c if the legacy procfs interface
is not enabled in the latest BK tree.

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

Updates for drivers/parisc.  Mostly conversion to generic device model.
New hppb driver from Ryan Bradetich.

Allow for per-CPU initialization of CPUfreq. Therefore, it's not
necessary any longer to kmalloc the per-CPU policy struct. To use
this, cpufreq_driver->policy has to be set to NULL. Of course,
cpufreq_driver->init is needed then, which is the appropriate function
for CPU initialization. cpufreq_driver->exit is available for cleanup.

All existing drivers continue to work without any changes, just for
clarity ->init and ->exit are set to NULL, and the names accordingly.

This reinstates the count parameter to store() methods.

This updates new cpufreq sysfs code to new rules.

  These two files needed to be touched after the recent changes to
DRIVER_ATTR/driver_attribute structure members in 2.5.56.  Personally,
it doesn't look to me like the size parameter should be removed, as now
users will need to hardcode PAGE_SIZE into their functions, rather than
it being passed from the place of allocation.  But I'm not familiar with
the driverfs changes, so can't really say.

These changes, or something similar, are needed to make ohci-dbg and
ehci-dbg work at all in 2.5.56.  ehci is untested, but compiles here.
I've tested the ohci changes and they appear to work.

The following patch provides minimal client support for the
(mandatory) Kerberos V5 authentication mechanism under RPCSEC_GSS.
See RFC2623 and RFC3010 for protocol details.

Only authentication is supported for the moment. Data integrity and/or
data privacy (encryption) will be implemented at a later stage.

This patches the RPCSEC_GSS client to make use of the upcall mechanism
that was provided by patch [3/6].

If an RPC task presents a non-uptodate credential to call_refresh(),
a user daemon is contacted by means of a dedicated rpc_pipefs pipe.
The daemon is then fed the uid for which it must establish a new RPCSEC
security context.

While the daemon goes about its business, the RPC task is put to sleep
on a wait queue in order to allow the 'rpciod' process to service other
requests. If another task wants to use the same credential, it too will
be put to sleep once it reaches call_refresh(). A timeout mechanism
ensures that requests are retried (or that 'soft' mounts fail) if the
daemon crashes / is killed.

Once the daemon has established the RPCSEC context, it writes the result
back to the pipe, causing the credential to be updated. Those RPC tasks
that were sleeping on the context are automatically woken up, and
their execution can proceed.

This patch provides the basic framework for RPCSEC_GSS authentication
in the RPC client. The protocol is fully described in RFC-2203.
Sun has supported it in their commercial NFSv3 and v2 implementations
for quite some time, and it has been specified in RFC3010 as being
mandatory for NFSv4.

  - Update the mount_data struct for NFSv2 and v3 in order to allow them
    to pass an RPCSEC_GSS security flavour. Compatibility with existing
    versions of the 'mount' program is ensured by requiring that RPCSEC
    support be enabled using the new flag NFS_MOUNT_SECFLAVOUR.
  - Provide secure authentication, and later data encryption on
    a per-user basis. A later patch will an provide an implementation
    of the Kerberos 5 security mechanism. SPKM and LIPKEY are still
    being planned.
  - Security context negotiation and initialization are all assumed
    to be done in userland. A later patch will provide the actual upcall
    mechanisms to allow for this.