2004-06-28 Margit Schubert-While <margitsw@t-online.de>

* Missing error check after dev_alloc_skb

2004-06-28 Margit Schubert-While <margitsw@t-online.de>

* Clean up function definitions (missing static, extraneous inline)

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

Patch from Nicolas Pitre

Missing prototype.

Patch from Nicolas Pitre

... and a comment fix in bonus

Patch from Tony Lindgren

Removes some dead code as noted by Russell King.

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

Signed-off-by: Kris Kersey <augustus@linuxhardware.org>
Signed-off-by: Dave Jones <davej@redhat.com>

Signed-off-by: Dave Jones <davej@redhat.com>

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

Use NULL, not 0, where appropriate.

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

- Remove 'arc' machine name from Makefile
- clk_set_rate() should return non-zero atm.
- proc-sa1100.S doesn't need asm/ptrace.h
- update mach-types
- kill line of spaces in clock.h

Generate SIZEOF_MACHINE_DESC using asm-offsets method rather than
relying on people updating the definition in asm/mach/arch.h

This places arch_adjust_zones along side ISA_DMA_THRESHOLD.  These
two are related, but having them in separate files means its not
obvious that they are.

ISA_DMA_THRESHOLD is a DMA mask which must be defined such that it
matches the memory handed out by GFP_DMA, which in turn is controlled
by arch_adjust_zones.

This allows machine classes to override ISA_DMA_THRESHOLD as
necessary.

Clean up bzImage target, remove a couple of obsolete testing targets,
and add better bootpImage help text.

This fixes the buggy decompressor assembly, and fixes PCMCIA IO
to use the correct byte lane when accessing certain PCMCIA cards.

Static data causes GOTOFF relocations to be used, which won't work
because we want to relocate the .data section separately from the
.text section.  Therefore, force all data to be nonstatic.

- use 'Image' target for kernel image to be compressed rather than
  duplicating its generation.
- use .incbin-based generation of ELF objects from binary data rather
  than 'ld'-based generation.

For clarity and consistency, use the same name for makefile and
linker symbols.

into hostme.bitkeeper.com:/repos/c/cifs/linux-2.5cifs

Since this is where these two variables are used, it makes sense to
have them in that makefile.  Also, consolidate "targets"
initialisation, fixes a missing FORCE dependency for the uImage rule,
and remove more FTVPCI code.

mm_struct.used_hugetlb used to eliminate costly find_vma() from
follow_page().  Now it is used only in ia64 version of follow_huge_addr(). 
I know nothing about ia64, but this REGION_NUMBER() looks simple enough to
kill used_hugetlb.

There is debug version (commented out) of follow_huge_addr() in i386 which
looks at used_hugetlb, but it can work without this check.
Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

radeonfb: fix 16bpp copyarea() bug

It turns out the bug was due to my mis-copying a certain set of flags from
the x.org tree.
Signed-off-by: David Eger <eger@havoc.gtf.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

When using gcc 3.3.3 on alpha, the current BK head doesn't compile.

- there's an external declaration for abs() in the same scope as a macro
  definition in arch/alpha/time.c

- The compiler is picky about `const' declarations, which breaks on
  bitops.h.
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

While writing some analysis tools for memory hot-remove, we came across a
single page which had a ->count that always increased, without bound.  It
ended up always being the zero page, and it was caused by a leaked
reference in some do_wp_page() code that ends up avoiding PG_reserved
pages.

Basically what happens is that page_cache_release()/put_page() ignore
PG_reserved pages, while page_cache_get()/get_page() go ahead and take the
reference.  So, each time there's a COW fault on the zero-page, you get a
leaked page->count increment.

It's pretty rare to have a COW fault on anything that's PG_reserved, in
fact, I can't think of anything else that this applies to other than the
zero page.

In any case, it the bug doesn't cause any real problems, but it is a bit of
an annoyance and is obviously incorrect.  We've been running with this
patch for about 3 months now, and haven't run into any problems with it.
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

<linux/fd.h> references __user which is defined in <linux/compiler.h>.
Signed-off-by: Tom Rini <trini@kernel.crashing.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>