into intel.com:/home/lenb/src/26-latest-dev

Implemented ACPI 3.0 support for implicit conversion within
the Match() operator. match_obj can now be of type
integer, buffer, or string instead of just type integer.
Package elements are implicitly converted to the type
of the match_obj. This change aligns the behavior of
Match() with the behavior of the other logical operators
(LLess(), etc.)  It also requires an errata change to the
ACPI specification as this support was intended for ACPI
3.0, but was inadvertently omitted.

Fixed a problem with the internal implicit "to buffer"
conversion.  Strings that are converted to buffers will
cause buffer truncation if the string is smaller than the
target buffer. Integers that are converted to buffers will
not cause buffer truncation, only zero extension (both as
per the ACPI spec.) The problem was introduced when code
was added to truncate the buffer, but this should not be
performed in all cases, only the string case.

Fixed a problem with the Buffer and Package operators
where the interpreter would get confused if two such
operators were used as operands to an ASL operator (such
as LLess(Buffer(1){0},Buffer(1){1}).  The internal result
stack was not being popped after the execution of these
operators, resulting in an AE_NO_RETURN_VALUE exception.

Fixed a problem with constructs of the form
Store(Index(...),...). The reference object returned from
Index was inadvertently resolved to an actual value. This
problem was introduced in version 20050114 when the
behavior of Store() was modified to restrict the object
types that can be used as the source operand (to match
the ACPI specification.)

Reduced stack use in acpi_get_object_info().

into ppc970.osdl.org:/home/torvalds/v2.6/linux

Patch from Thomas Gleixner

Remove NULL initializers of static variables.

Signed-off-by: Thomas Gleixner
Signed-off-by: Russell King

Patch from Thomas Gleixner

Trivial build fix for shannon platform

Signed-off-by: Thomas Gleixner
Signed-off-by: Russell King

Patch from Thomas Gleixner

Trivial build fix for badge4 platform

Signed-off-by: Thomas Gleixner
Signed-off-by: Russell King

into ppc970.osdl.org:/home/torvalds/v2.6/linux

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

Fixes MDIO delay. Please apply.
Signed-off-by: Ralph Siemsen <ralphs@netwinder.org>
Signed-off-by: Matt Porter <mporter@kernel.crashing.org>
Signed-off-by: Jeff Garzik <jgarzik@pobox.com>

Fixes a bug in RX buffer allocation so that jumbo size skbs are
allocated when the MTU size is changed. Also removes the deprecated
restore_flags() call.  Please apply.
Signed-off-by: Matt Porter <mporter@kernel.crashing.org>
Signed-off-by: Jeff Garzik <jgarzik@pobox.com>

Really.

This makes it possible to mark binaries to have both an executable stack
and heap, allowing for a NX system to disable NX on a per-binary level.
Signed-off-by: Arjan van de Ven <arjan@infradead.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

The dynamic clock code in radeonfb comes almost as-is from X.org (where
it was contributed by ATI). It has a few typos (wrong register access
macros) that this patch fixes.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

A simple 'grep memset.*\<0);' shows argument order errors in several
uses of memset.

This grep was inspired by Al Viro's recent patch, megaraid_mbox fix,
which fixed this problem in the megaraid driver.

This removes the CRs from the kernel file of Eicon ISDN driver.

into ppc970.osdl.org:/home/torvalds/v2.6/linux

Patch from Ben Dooks

Off by 4 error on S3C2440_CAMDVIN register address, and
re-indented the pll calculation code to proper C style.
Thanks to Guillaume Gourat for spotting the register mistake

Signed-off-by: Guillaume Gourat

Signed-off-by: Ben Dooks
Signed-off-by: Russell King

Patch from Ben Dooks

GPIOJ12 alternate function is CAMRESET, not CAMCLKOUT
as mis-copied on creation
Patch from Guillaume Gourat

Signed-off-by: Guillaume Gourat

Signed-off-by: Ben Dooks
Signed-off-by: Russell King

Patch from Lennert Buytenhek

The alignment trap handler in arch/arm/mm/alignment.c performs halfword
and word accesses by translating them into byte accessing and then
combining the pieces.  However, it assumes little-endian byte ordering
in doing so, which causes unaligned accesses on big-endian platforms
to erroneously load or store byteswapped data.
This patch was pulled from an old 2.4 -ds tree, and appears to fix the
issue.  It was submitted for 2.4 at the time (ARM patch ID 1205/1206),
but rejected since big-endian ARM platforms are not supported in 2.4.

Signed-off-by: Lennert Buytenhek
Signed-off-by: Russell King

For device memory, just return a value that will never
cause pte_pfn() to return true.

Noticed by Tom Callaway.
Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: David S. Miller <davem@davemloft.net>

This fixes the raid5 and raid6 prolems that crept in with the recent
introduction of "bi_max_vecs".

Since raid5/raid6 allocate their own bio's, they need to make sure
that bi_max_vecs is updated along with bi_vcnt.

Don't use pci_dev->irq until after pci_enable_device().
Andy Esten reported that his NIC stopped working in
2.6.10 because of this problem.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: Jeff Garzik <jgarzik@pobox.com>

wrong order of arguments in memset().

This, BTW, shows why cross-builds are useful - the only indication of
problem had been a new warning showing up in sparse output on alpha
build (number exceeding 256 got truncated).
Signed-off-by: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>

The vmap vmalloc rework in 2.5 had a unintended side effect.  vmalloc uses
kmalloc now to allocate an array with a list of pages.  kmalloc has a 128K
maximum.  This limits the vmalloc maximum size to 64MB on a 64bit system
with 4K pages.  That limit causes problems with other subsystems, e.g.
iptables relies on allocating large vmallocs for its rule sets.

This is a bug IMHO - on 64bit platforms there shouldn't be such a low limit
on the vmalloc size.  And even on 32bit it's too small for custom kernels
with enlarged vmalloc area.

Another problem is that this makes vmalloc unreliable.  After the system
has been running for some time it is unlikely that kmalloc will be able to
allocate >order 2 pages due to memory fragmentation.

This patch takes the easy way out for fixing this by just allocating this
array with vmalloc when it is larger than a page.  While more complicated
and intrusive solutions would be possible they didn't use vmalloc
recursively they didn't seem it worth to handle this very infrequent case.

Please note that the vmalloc recursion is strictly bounded because each
nested allocation will generate a much smaller stack frame.  Also the
kernel stack can handle even a few recursion steps easily because vmalloc
has only a small stack frame.
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

This patch removes excess '~' before the bit masks.
Signed-off-by: Andrei Konovalov <akonovalov@ru.mvista.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

dma_declare_coherent_memory() is calling kmalloc with wrong arguments.
Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

This fixes an issue related to the second PCI host controller working on
MPC8555/41 systems.

We track the last PCI bus number on PCI1 so that the PCI2 host
controller can properly exclude itself at the right time, exclusion
should occur after initial setup so that the early pci config cycles in
setting PCI2 actually get to the controller. 
Signed-off-by: Kumar Gala <kumar.gala@freescale.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

into ppc970.osdl.org:/home/torvalds/v2.6/linux

into ppc970.osdl.org:/home/torvalds/v2.6/linux

Cleanups (initially sent by Adrian Bunk):
 - make some needlessly global code static
 - removed obsolete #define OLD_MAX_DESCRIPTORS
 - removed more platform independend code not used in linux
 - removed dos-<CR> at end of lines 
 - fix indentation in already modified files
Signed-off-by: Armin Schindler <armin@melware.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

convert from pci_module_init to pci_register_driver
Signed-off-by: Christophe Lucas <c.lucas@ifrance.com>
Signed-off-by: Armin Schindler <armin@melware.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

My recent do_munmap hugetlb fix has proved inadequate.  There are
other places (madvise, mbind, mlock, mprotect) where split_vma is
called.  Only mprotect excludes a hugetlb vma: the others are in
danger of splitting at a misaligned address, causing later BUGs.

So move the ~HPAGE_MASK check from do_munmap to split_vma itself;
and fix up those places (madvise and mlock) which expect split_vma
can fail only with -ENOMEM, and wish to convert that to -EAGAIN.
(It appears genuine that some of these syscalls should be failing
with -ENOMEM and some with -EAGAIN, so respect those behaviours.)

madvise_dontneed doesn't use split_vma, but is equally in danger
of causing a hugetlb BUG via zap_page_range.  Whereas elsewhere the
patch is permissive (allowing the operation on a hugetlb vma even when
pointless, so long as it doesn't missplit it), here we must use -EINVAL
on any hugetlb vma, since a page fault would hit the BUG in its nopage.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
Acked-by: William Irwin <wli@holomorphy.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Signed-off-by: David S. Miller <davem@davemloft.net>

This patch fixes the problem reported in:

http://marc.theaimsgroup.com/?l=linux-kernel&m=110798711911645&w=2


The 5700 link problem was caused by reading uninitialized values in sram and
causing capacitive coupling mode to be enabled by mistake. This patch fixes
the problem by properly validating the sram contents.
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

This fixes the mincore syscall in three ways:

 (1) It moves as much argument checking outside of the semaphore-holding
     region as possible.

 (2) It checks the region parameters against TASK_SIZE so that a 32-bit binary
     on a 64-bit platform will get the right error when calling this syscall
     on a region that overlaps the end of the 32-bit address space.

 (3) It tidies up the VMA checking loop a little.
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-Off-By: Linus Torvalds <torvalds@osdl.org>

The attached patch fixes sigaltstack handling for RT signal return. It was
reading a userspace struct into kernel space and then passing the kernel copy
to a generic signalling routine which then assumed it had been passed a
userspace pointer...
Signed-Off-By: David Howells <dhowells@redhat.com>
Signed-Off-By: Alexander Viro <aviro@redhat.com>
Signed-Off-By: Linus Torvalds <torvalds@osdl.org>