[Lucid][pull request] Update to 2.6.32.15/16 Stable Kernel

Stefan Bader stefan.bader at canonical.com
Tue Jul 27 12:16:51 UTC 2010


On 07/26/2010 09:19 PM, Steve Conklin wrote:
> On Mon, 2010-07-26 at 13:12 -0600, Tim Gardner wrote:
>> On 07/21/2010 07:17 AM, Steve Conklin wrote:
>>> Hi All,
>>>
>>> http://bugs.launchpad.net/bugs/607824
>>>
>>> The 2.6.32.16 stable kernel has recently been released.
>>>
>>> http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.32.16
>>> http://kernel.org/pub/linux/kernel/v2.6/patch-2.6.32.16.bz2
>>>
>>> The 2.6.32.16 upstream stable kernel brings in 143 patches
>>> (DRM excluded).
>>>
>>> As we carry the DRM stack from 2.6.33, all patches that affect
>>> DRM have been dropped and replaced by DRM patches from 2.6.33.6
>>> (9 patches).]
>>>
>>> The upstream process for stable tree updates is quite similar
>>> in scope to the Ubuntu SRU process. e.g: each patch demonstrably
>>> fixes a bug and is vetted by upstream either by originating
>>> directly from Linus' tree or by being minimally backported from
>>> some patch in Linus' tree.
>>>
>>>
>>> TEST CASE: TBD
>>>
>>> The following patches were already in our tree, and have been
>>> reverted and replaced by the version from stable:
>>>
>>> * PCI quirk: Disable MSI on VIA K8T890 systems
>>> * PCI quirks: disable msi on AMD rs4xx internal gfx bridges
>>> * UBUNTU: SAUCE: tulip: Let dmfe handle davicom on non-sparc
>>> * Attempt #2 to handle null nameidata
>>> * tipc: Fix oops on send prior to entering networked mode (v3)
>>> * (pre-stable) Input: psmouse - reset all types of mice before
>>> reconnecting
>>> * jbd: jbd-debug and jbd2-debug should be writable
>>>
>>> I am attaching the review and I have pushed a preview tree to
>>>
>>> git://kernel.ubuntu.com/sconklin/ubuntu-lucid.git stable-16
>>>
>>> http://kernel.ubuntu.com/git?p=sconklin/ubuntu-lucid.git;a=shortlog;h=refs/heads/stable-16
>>>
>>> This set of patches required an ABI bump.
>>>
>>>
>>>
>>>
>>>
>>
>> So, whats the hold up? Are you still waiting on a security update?
> 
> Yes, as soon as the security update lands we'll apply these.
> 

Oh, Steve, one thing that completely slipped my notice previously. The topic
should be Update to 2.6.32.16 stable kernel. The 15/16 notation was something I
only did once or twice when I used one tracking bug for two stable updates (when
the second update was just a single patch to fix a hot issue).

-Stefan




More information about the kernel-team mailing list