1/8 definitions of CONFIG_VGA_CONSOLE have trivially different banners.

 The CRIS architecture is also able to use the generic
 copy_siginfo_to_user.

 init_rootfs() (from ramfs) doesn't appear in any header file.  I didn't
 see any that looked like a good home, so lets put a prototype at the top
 of fs/namespace.c.  This only use of this function is in namespace.c.

 Symbol CONFIG_SOFTWARE_SUSPEND depends on CONFIG_EXPERIMENTAL but does
 not say so in its banner.

 this patch fixes redundant declarations in 2.5.24
 (same as sent yesterday, but this time automacially splitted
 into several mails)

 Details over 2 years out of date.

  The arch-determining symbol CONFIG_SH in drivers/mtd/maps/Config.in
  should be CONFIG_SUPERH.

  [Rusty: this is a resend of 'PATCH 2.5: kconfig wrong arch symbol';
   it should apply now that my earlier patch which trod on the context
   has been merged into 2.5.24]

 Use of the $ARCH variable is undocumented; the alpha port defines the
 bool constant CONFIG_ALPHA for this purpose.

 Symbol CONFIG_SGI_NEWPORT_GFX depends on CONFIG_EXPERIMENTAL but does
 not say so in its banner.

 attached patch adds missing static modifiers for small_digits[] and
 large_digits[] arrays in the number() function from lib/vsprintf.c

 Patch against 2.5.25, should apply to 2.4.x.
 Please consider applying.

 Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
 define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
 for this purpose.

 Use of the $ARCH variable is undocumented; the sparc and sparc64 ports
 define the bool constants CONFIG_SPARC32 and CONFIG_SPARC64 respectively
 for this purpose.

 This patch was included in 2.5.23, but removed in 2.5.24.  I guess
 I should have sent it to the maintainer in the first place ...

 This allows the cs46xx driver to build.

 this patch fixes redundant declarations in 2.5.24
 (same as sent yesterday, but this time automacially splitted
 into several mails)

Beffers marked for async io must be locked!

  After getting rid of rpc_lock_task() from net/sunrpc/xprt.c (see the
previous patch), we can now remove it from the generic RPC queue
handling code.

  Divorces task xid<->request slot mapping from the internals of the
rpc_waitqueue xprt->pending. Instead xprt_lookup_rqst() is made to
search a dedicated list (xprt->recv) on which the request slot is
placed immediately after being allocated to a task. The new queue is
protected using the spinlock xprt->sock_lock rather than the generic
RPC task lock.

  Both udp_data_ready() and tcp_data_ready() (well tcp_read_request()
actually) now need to protect against the request being removed from
the xprt->recv list while they copy the RPC reply data from the skb.
On the other hand, they no longer need to worry about the task
disappearing from xprt->pending. This means that rpc_lock_task() hack
can be replaced by the spinlock xprt->sock_lock.

  Fixes an obvious bug in __nfs_refresh_inode(): after updating the
attribute cache, if we discover that the data cache is invalid don't
call nfs_zap_caches() as that will also reinvalidate the attribute
cache.
  This bug plays havoc with the new lookup/revalidation code in 2.4.19
since it forces a lot of unnecessary extra GETATTR RPC calls.

This patch is against lk 2.5.25 . It
  - fixes copy_from/to_user() [William Stinson from dj tree]
  - disables kiobuf use, so it will compile without kiobufs

The latter change is so Andrew Morton can remove kiobufs
as suggested in his "direct-to-BIO for O_DIRECT" thread.

 - Make airo include tqueue.h, which is needed to make this driver
   compile at all again.

 - Adjust aztcd.c and sonycd535.c to the recent end_request() signature
   changes.

From Andi Kleen:

Some fixes for CONFIG_X86_MCE_NONFATAL

Calling smp_call_function from interrupt context is forbidden

Unless I'm mistaken it would BUG on any box with more than two CPUs because
it would expect smp_call_function callback to run only on a single CPU??

Also handle the Hammer.

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

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

SuSv3 says: "The mprotect() function shall fail if:

  [EACCES]
    The prot argument specifies a protection that violates the access
    permission the process has to the underlying memory object.

  [EAGAIN]
    The prot argument specifies PROT_WRITE over a MAP_PRIVATE mapping and
    there are insufficient memory resources to reserve for locking the
    private page.

  [EINVAL]
    The addr argument is not a multiple of the page size as returned by
    sysconf().

  [ENOMEM]
    Addresses in the range [addr,addr+len) are invalid for the address
    space of a process, or specify one or more pages which are not mapped.

  [ENOMEM]
    The prot argument specifies PROT_WRITE on a MAP_PRIVATE mapping, and
    it would require more space than the system is able to supply for
    locking the private pages, if required.

  [ENOTSUP]
    The implementation does not support the combination of accesses
    requested in the prot argument."

This fixes error code of mprotect() of the ENOMEM case.

SuSv3 says: "The msync() function shall fail if:

[EBUSY]
    Some or all of the addresses in the range starting at addr and
    continuing for len bytes are locked, and MS_INVALIDATE is
    specified.

[EINVAL]
    The value of flags is invalid.

[EINVAL]
    The value of addr is not a multiple of the page size {PAGESIZE}.

[ENOMEM]
    The addresses in the range starting at addr and continuing for len
    bytes are outside the range allowed for the address space of a process
    or specify one or more pages that are not mapped."

This fixes error code of msync() of the EINVAL case.

A partitioned ppc64 machine can have a boot cpuid anywhere from 0 to 31.
With the non linear cpu changes in 2.5.24 we must set up the initial task
to start on the boot cpu. (since it isnt always 0 now)

With this patch I am able to boot on cpus other than 0. I also tested
discontiguous cpuids. So the non linear cpu stuff checks out OK.

I introduced warning about 3 releases ago. This prototypes are
actually unneccessary and killing them makes warning go away. Please
apply,

I'd like Florent credited -- he is maintaining 2.4.X version and
helping with development. Kill warnings by rearranging code / adding
prototypes. Enable using separate console (so user sees progress and X
suspend/resume works properly), forward-port of updates from Florent
and stop using own PRINTK stuff (mostly). Reading now primarily uses
block_device(), this should enable more cleanups. Fixed double free on
error path.

This fixes a problem introduced by the pageattr ioremap/unmap patches.
iounmap lost the ability to free non page aligned addresses, which
are e.g. used by the bootflag code.  This patch fixes this.

Also fix a potential off by one bug.

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

This patch for 2.5.25 is a rewrite of how smbfs builds requests. It allows
for more parallellism, better error handling and supporting oplocks with
further patches.

This was found by Dan Carpenter <error27@email.com>, using an smatch
script.  Looks to me like like an error caused during all the BKL
pushing.  1 more coming...

Not tested (Greg, please don't hurt me :p )