merge 2.6.13-rc4 with ACPI's to-linus tree

   memory regions in-use. The name argument should be a pointer to

   your driver name. Eg, for pcnet_cs, name should point to the

   string "pcnet_cs".

* CardServices is gone

  CardServices() in 2.4 is just a big switch statement to call various

  services.  In 2.6, all of those entry points are exported and called

  directly (except for pcmcia_report_error(), just use cs_error() instead).

* struct pcmcia_driver

  You need to use struct pcmcia_driver and pcmcia_{un,}register_driver

  instead of {un,}register_pccard_driver

	  3stack-digout	3-jack in back, a HP out and a SPDIF out

	  5stack	5-jack in back, 2-jack in front

	  5stack-digout	5-jack in back, 2-jack in front, a SPDIF out

	  6stack	6-jack in back, 2-jack in front

	  6stack-digout	6-jack with a SPDIF out

	  w810		3-jack

	  z71v		3-jack (HP shared SPDIF)

	  asus		3-jack

	  uniwill	3-jack

	  F1734		2-jack

	  test		for testing/debugging purpose, almost all controls can be

			adjusted.  Appearing only when compiled with

			$CONFIG_SND_DEBUG=y

	CMI9880

	  minimal	3-jack in back

    The power-management is supported.

  Module snd-pxa2xx-ac97 (on arm only)

  ------------------------------------

    Module for AC97 driver for the Intel PXA2xx chip

    For ARM architecture only.

  Module snd-rme32

  ----------------

    Module supports up to 8 cards.

  Module snd-sun-dbri (on sparc only)

  -----------------------------------

    Module for DBRI sound chips found on Sparcs.

    Module supports up to 8 cards.

  Module snd-wavefront

  --------------------

  Module snd-vxpocket

  -------------------

    Module for Digigram VX-Pocket VX2 PCMCIA card.

    Module for Digigram VX-Pocket VX2 and 440 PCMCIA cards.

    ibl      - Capture IBL size. (default = 0, minimum size)

    Note: the driver is build only when CONFIG_ISA is set.

  Module snd-vxp440

  -----------------

    Module for Digigram VX-Pocket 440 PCMCIA card.

    ibl      - Capture IBL size. (default = 0, minimum size)

    Module supports up to 8 cards.  The module is compiled only when

    PCMCIA is supported on kernel.

    To activate the driver via the card manager, you'll need to set

    up /etc/pcmcia/vxp440.conf.  See the sound/pcmcia/vx/vxp440.c.

    When the driver is compiled as a module and the hotplug firmware

    is supported, the firmware data is loaded via hotplug automatically.

    Install the necessary firmware files in alsa-firmware package.

    When no hotplug fw loader is available, you need to load the

    firmware via vxloader utility in alsa-tools package.

    About capture IBL, see the description of snd-vx222 module.

    Note: the driver is build only when CONFIG_ISA is set.

  Module snd-ymfpci

  -----------------

their work on their own time, asking programmers to do extra work for no

gain, for free, is not a possibility.

Security issues are also a very important for Linux.  When a

Security issues are also very important for Linux.  When a

security issue is found, it is fixed in a very short amount of time.  A

number of times this has caused internal kernel interfaces to be

reworked to prevent the security problem from occurring.  When this

Everything you ever wanted to know about Linux 2.6 -stable releases.

Rules on what kind of patches are accepted, and what ones are not, into

the "-stable" tree:

 - It must be obviously correct and tested.

 - It can not bigger than 100 lines, with context.

 - It must fix only one thing.

 - It must fix a real bug that bothers people (not a, "This could be a

   problem..." type thing.)

 - It must fix a problem that causes a build error (but not for things

   marked CONFIG_BROKEN), an oops, a hang, data corruption, a real

   security issue, or some "oh, that's not good" issue.  In short,

   something critical.

 - No "theoretical race condition" issues, unless an explanation of how

   the race can be exploited.

 - It can not contain any "trivial" fixes in it (spelling changes,

   whitespace cleanups, etc.)

 - It must be accepted by the relevant subsystem maintainer.

 - It must follow Documentation/SubmittingPatches rules.

Procedure for submitting patches to the -stable tree:

 - Send the patch, after verifying that it follows the above rules, to

   stable@kernel.org.

 - The sender will receive an ack when the patch has been accepted into

   the queue, or a nak if the patch is rejected.  This response might

   take a few days, according to the developer's schedules.

 - If accepted, the patch will be added to the -stable queue, for review

   by other developers.

 - Security patches should not be sent to this alias, but instead to the

   documented security@kernel.org.

Review cycle:

 - When the -stable maintainers decide for a review cycle, the patches

   will be sent to the review committee, and the maintainer of the

   affected area of the patch (unless the submitter is the maintainer of

   the area) and CC: to the linux-kernel mailing list.

 - The review committee has 48 hours in which to ack or nak the patch.

 - If the patch is rejected by a member of the committee, or linux-kernel

   members object to the patch, bringing up issues that the maintainers

   and members did not realize, the patch will be dropped from the

   queue.

 - At the end of the review cycle, the acked patches will be added to

   the latest -stable release, and a new -stable release will happen.

 - Security patches will be accepted into the -stable tree directly from

   the security kernel team, and not go through the normal review cycle.

   Contact the kernel security team for more details on this procedure.

Review committe:

 - This will be made up of a number of kernel developers who have

   volunteered for this task, and a few that haven't.

  notsc

  Don't use the CPU time stamp counter to read the wall time.

  This can be used to work around timing problems on multiprocessor systems

  with not properly synchronized CPUs. Only useful with a SMP kernel

  with not properly synchronized CPUs.

  report_lost_ticks

  Report when timer interrupts are lost because some code turned off

  event. This will make the CPUs eat a lot more power, but may be useful

  to get slightly better performance in multiprocessor benchmarks. It also

  makes some profiling using performance counters more accurate.

  Please note that on systems with MONITOR/MWAIT support (like Intel EM64T

  CPUs) this option has no performance advantage over the normal idle loop.

  It may also interact badly with hyperthreading.

Rebooting

  noreplacement  Don't replace instructions with more appropiate ones

		 for the CPU. This may be useful on asymmetric MP systems

		 where some CPU have less capabilities than the others.