parport_announce_port() was always called right after
parport_proc_register().  Call shifted into parport_announce_port().
Similar for parport_remove_port() and parport_proc_unregister().

	parport_unregister_port() is split; parport_remove_port() does
what parport_unregister_port() used to do sans the final parport_put_port()
call.
	Callers updated; many of them needed only parport_put_port() (failure
exit paths where we never had the port announced to drivers).
	Fixed multiple races on port removal by shifting parport_remove_port()
in front of the code that releases irq/io ports/etc.

	references to slave ports of mux added to struct parport.
parport_daisy_init() doesn't go through parport_announce_port() for mux
slaves anymore; parport_annouce_port() deals with found ones itself.
Error handling sanitized, races on unregistration fixed.

	parport_pc_probe_port() sanitized; leaks fixed.

	parport_pc options parsing moved to parport_pc.c; parport/init.c is
gone.
	Warning fixes from -mm added.

	Registration of sysctls turned into module_init().

	Init of low-level drivers (except parport_pc) turned into module_init().

	Exports moved from parport/init.c to files where functions are
actually defined.

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

into sgi.com:/source2/xfs-linux-2.6

SGI Modid: xfs-linux:xfs-kern:167581a

padding to ic_roundoff to cater for pad in reservation cursor updates.

SGI Modid: xfs-linux:xfs-kern:167580a

SGI Modid: xfs-linux:xfs-kern:167547a

SGI Modid: xfs-linux:xfs-kern:167442a

SGI Modid: xfs-linux:xfs-kern:166619a

SGI Modid: xfs-linux:xfs-kern:167279a

SGI Modid: xfs-linux:xfs-kern:167273a

SGI Modid: xfs-linux:xfs-kern:167222a

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

Which is a lot simpler than the two-way counter implementation.

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

into kroah.com:/home/linux/BK/pci-2.6

This patch contains the following:
1.  Fix up the pcie and shpc options to make it easier for distros
    to use as what we have discussed;
2.  Fix bug encountered when installing the drivers on non-hotplug
    systems;
3.  Put PCI_CAP_ID_SHPC in include/linux/pci.h

into kroah.com:/home/linux/BK/driver-2.6

Fix two OHCI unlink issues.

   * All EDs now get a 1 msec delay before re-linking, even those
     which were seemingly "clean" unlink cases.  This gets rid of
     some list corruption issues ("bad entry") by getting rid of
     a fast-path carried over from 2.4 usb-ohci.

   * In case of unlink-during-submit, we must giveback() right away.
     This is a reasonably rare case.

There have been recent reports of problems here.  The "bad entry"
showed up with usbtest tests #11 and #12, or "stir4200", and maybe
in other cases.  The unlink-during-submit shows up in usbtest.

The DACA sound driver (early iBook models) doesn't clear the i2c_client
structure. That cause the embedded struct device (and thus kobject) to
contain garbage in the "k_name" field, which kobject_set_name will
later try to kfree...

Also remove references to unused struct data_data.

Thanks to Linda Xie for pointing this out.

Here is a small ISDN fix for the current tree.

There is a compiler inlining/optimation problem with strpbrk, if it has
only a one character search string.  This results in a missing strchr
because the compiler internally replace strpbrk with strchr in this
case, but did so after inline handling stage.

A small birdie tells us that in the long run it may not be a good idea
to write the APIC ID register.  It might be read-only in some
hypothetical situation down the road.

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

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

From: Philippe Elie <phil.el@wanadoo.fr>

When I debugged P4 ht oprofile a few month ago I noticed that but though it
wasn't a problem...  The fix I propose is not completely clean.

With P4 HT we split msr in two subset, one for each logical processor.  The
msrs subset used in op_model_p4.c at save and setup point of view are
distinct (*), it means we must serialize setup and save operation else a
logical processor can save some msr value already setup by the other thread
then when oprofile shutdown we restore wrong msrs values.

Nobody noticed the problem because after restoring the msrs we call
enable_lapic_nmi_watchdog() -> setup_p4_watchdog() wich clear all the msrs
but it's a bit fragile.  If nmi watchdog is not enabled nothing bad occurs
because the LVTPC remains disabled.

(*) this is done in this way because it allows a lot of simplification in
op_model_p4.c, yes it isn't clean but it's not fixable w/o rewriting 75% of
op_model_p4.c and I think the code will be bigger and more complex.