this is only for the module-related warning introduced by my
__deprecated patch.

journal_init_common is always called from ext3 which already makes
jbd.ko unloadable by relying on exported functions.

shorter and/or more descriptive choice names, add a full (tho still
commented out entry) for the visw, based on the 2.4 Configure.help
entry.

The strtab section is supposed to be found using the symtab's
sh_link field, not by name.

Add a const declaration to the __module_param_call so __param section
gets more correct attributes.

	Rather than have the module loader the module structure and
resolve the symbols __this_module to it, make __this_module a real
structure inside the module, using the linkonce trick we used for
module names.

	This saves us an allocation (saving a page per module on
archs which need the module structure close by), and means we don't
have to fill in a few module fields.

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

Only one of wakeup_secondary_via_NMI() and wakeup_secondary_via_INIT() is
needed.  We're currently compiling both, which generates an unused function
warning.

These functions have no references.  Just ifdef them away for now; someone
may want them back.

drivers/serial/core.c:390: warning: `quot' might be used uninitialized in this function

It's a compiler bug.  This change makes it go away.

Ingo added saved_fs, saved_gs to thread_struct and didn't add
corresponding initializers to INIT_THREAD.  We assign NULL to an
unsigned int and the compiler warns.

The patch converts it to use designated initialisers and fixes the
io_bitmap initializer in the process.

A second start at removing them from kernel/*.c and fs/*.c.

Note that module_put is fine for a NULL argument.

Rename the deprecated attribute to __deprecated to make it obvious
this is something special and to avoid namespace clashes.

Mark old module interfaces deprecated.

The use of explicit initializers all over the i2c core anoyed for
long, but the lm_sensors merge with two new files just for initializers
was too much.  Conver all of i2c to sane initialization (mostly
initcall, but some driver also got other cleanups in that area)

Trying to get the i2c code in shape at some point..

This is a large rewrite of i2c-amd756 (added by Pavel post 2.5.53
although it's not his code) into a driver following linux driver
guide lines.  As a side-effect it shrinks the driver by almost one
fifth.  Tested with an early AMD756-based board.

 - use proper PCI API
 - use pr_debug instead of #ifdef DEBUG mess
 - use named initializers
 - completly restructure init/exit code
 - mark everything static

So stub it out, similar to /proc/<pid>/wchan for !CONFIG_KALLSYMS

It's only used to hide two entries in arch/i386/Kconfig.

inline asm will do it for us.

This corrects the misspellings of "deprecated" in a few places.

This moves ramfs_getattr() to fs/libfs.c as simple_getattr()

doing a full register restore on return to user space, and thus require
the long system call exit path (ie "iret" instead of "sysexit").

 * execve() - we need to set edx/ecx correctly at process startup.
 * iopl() - needs iret to restore eflags with new IOPL levels.

Here's a fix on top of the patch you commited:

  - Rename ide_intr_lock to falconide_intr_lock
  - Add falconide_intr_lock to the Falcon IDE driver itself
  - Test for CONFIG_BLK_DEV_FALCON_IDE instead of CONFIG_ATARI since
    falconide_intr_lock is Falcon IDE-specific, not Atari-specific

This makes ramfs support proper st_blocks accounting.

a bit more closely.

This marks check_region "deprecated".

This gives a nice warning messages for programs that still use
check_region for example:

 drivers/parport/parport_pc.c:2215: warning: `__check_region' is deprecated (declared at include/linux/ioport.h:111)

This patch adds support for usage of the attribute as "deprecated" and
is backward-compatible.  Usage is:

	int deprecated foo(void)

etc..

If we mark a function as deprecated, then each use of the function emits
a warning like:

	foo.c:12: warning: `baz' is deprecated (declared at bar.c:60)

Which is very informative, giving both the location of each usage and
where the little bastard is declared.

Rusty missed this one.

Switch to larger operating GDT after moving to protected mode

This is necessary to boot on certain subarchs (voyager)

Also localises the parameters and setup into kernel/timers

Adds an external flag so that the tsc can be disabled from the
machine specific setup (used by voyager)

Patch suggested by Randy Dunlap