le16_to_cpu() on 32bit field.
Signed-off-by: Al Viro <viro@parcelfarce.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Use of 16bit little-endian in comparisons and arithmetics without
conversion. 
Signed-off-by: Al Viro <viro@parcelfarce.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

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

$(addprefix ...) needs a directory relative to current directory, because
kbuild prefixes the filename with '$(obj)/'
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>

 a) upper 32 bits of cpu_to_le64(x) are *not* cpu_to_le32(x) of
    upper 32 bits.
 b) ->ByteCount cleaned up.
Signed-off-by: Al Viro <viro@parcelfarce.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

cpu_to_le32(...) assigned to 16bit fields.

Signed-off-by: Tom Rini <trini@kernel.crashing.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Just test the end case inside the loop, rather than trying to
be clever and getting it wrong.

The previous single-step patch ("make single-step into signal delivery
stop in handler") took things a little too far. 

It left TF set in the sigcontext on the stack, so a PTRACE_CONT after
stopping at the handler entry will step instead of resume.  This
additional patch fixes it. 
Signed-off-by: Roland McGrath <roland@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

timer_create leaks task_structs.  I probably introduced this bug when I did
the cleanup making posix-timers properly per-process.  This patch fixes it.

There is also a fixup for a random indentation snafu at the end.
Signed-off-by: Roland McGrath <roland@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

    Helps to keep the 'sendmail' doctor away.
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
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

into flint.arm.linux.org.uk:/usr/src/bk/linux-2.6-rmk

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

Patch from Ian Campbell

Please ignore previous patch: set_irq_type takes the IRQ number and
not the GPIO number so using any variant on IRQ_TO_GPIO* is incorrect
anyway.
Signed-of-by: Ian Campbell <icampbell@arcom.com>

Patch from Nicolas Pitre

- Don't chain assignment to volatile registers.
  Doing otherwise generates extra needless code to reload the value
  for the next assignment.

- Don't touch PXA27x registers on a PXA25x build.
  (spotted by Ian Campbell)

Signed-off-by: Nicolas Pitre 

 CONFIG_ARCH_IOP3XX

Patch from Nicolas Pitre

Signed-off-by: Nicolas Pitre 

Basic serial ports, acpi and intel sound.

Can you guess what my laptop has in it?

There's tons of mis-use of PCI memory-mapped IO that is used
as if it was regular memory. That fails disastrously on a number
of architectures, and it doesn't help that it just happens to
work on regular x86 boxes.

This makes makes us do much stricter type-checking. Some of it
visible to the regular compiler, but the bulk of it is for sparse.

Signed-off-by: Thomas Graf <tgraf@suug.ch>
Signed-off-by: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

We run into a potential problem if we are doing
TSO and we reduce the congestion window.  We might
create a case where the TSO packet is what we need
to resend but the congestion window is not large
enough to allow it through.

The fix is very simple, since tcp_retransmit_skb()
is going to chop the size of the packet down to size
of the normal non-TSO MSS, we can pretend at the top
level that each SKB is composed of only one real MSS
worth of data.
Signed-off-by: David S. Miller <davem@davemloft.net>

Calls to tcp_fragment() change the tso_factor of
an SKB, so we need to deal with that.
Signed-off-by: David S. Miller <davem@davemloft.net>

Do not reference the tso_factor of SKB buff until
it is initialized.
Signed-off-by: David S. Miller <davem@davemloft.net>

Signed-off-by: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

If we don't have IPv6 default routes, we assume all ipv6 destinations 
are on-link as specified in RFC2461. It, however, is considered harmful now;
it is problematic with IPv6-capable nodes that do not have off-link
IPv6 connectivity (eg no default routers) and such nodes will take
a few seconds until they fall back to use IPv4.

See <draft-ietf-v6ops-onlinkassumption-02.txt> for details.

From: KUNITAKE Koichi <kunitake@anchor.jp>
Signed-off-by: KUNITAKE Koichi <kunitake@anchor.jp>
Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Signed-off-by: David S. Miller <davem@davemloft.net>