From: Jiri Slaby <jslaby@suse.cz>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
lwn@lwn.net, Willy Tarreau <w@1wt.eu>,
Bjorn Helgaas <bhelgaas@google.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Linux 2.6.32.55
Date: Fri, 22 Jun 2012 23:10:25 +0200 [thread overview]
Message-ID: <4FE4DF41.30400@suse.cz> (raw)
In-Reply-To: <20120622193824.GA3371@kroah.com>
On 06/22/2012 09:38 PM, Greg KH wrote:
> On Fri, Jun 22, 2012 at 09:04:03PM +0200, Jiri Slaby wrote:
>> On 01/25/2012 11:34 PM, Greg KH wrote:
>>> I'm announcing the release of the 2.6.32.55 kernel.
>> ...
>>> Bjorn Helgaas (1): PNP: work around Dell 1536/1546 BIOS MMCONFIG
>>> bug that breaks USB
>>
>> Hi, this one is dependant on 24d25dbfa63c3 (x86/PCI: amd: factor out
>> MMCONFIG discovery), otherwise amd_get_mmconfig_range is undefined...
>
> Interesting that this was reported almost 6 months after it was released :)
Yes :). This is because it is inside #ifdef CONFIG_AMD_NB which perhaps
nobody has set in 2.6.32. (Other than that we have the kernel in suse
enterprise for some time already.)
@Willy: 24d25dbfa63c3 is not enough. The header referenced in
2.6.32.55's patch does not exist in that tree yet. It was renamed from
asm/k8.h to asm/amd_nb.h later (by 23ac4ae827e62).
Given nobody noticed till now, I would incline to drop that patch from
2.6.32 series. Opinions?
> Anyway, I'm no longer handling 2.6.32 kernel stuff anymore, so there's
> nothing I can do here, sorry.
Yeah, I see, I replied to the announcement and added Willy. Your email
was @ suse, so you should have not received a copy anyway :).
thanks,
--
js
suse labs
next prev parent reply other threads:[~2012-06-22 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 22:34 Linux 2.6.32.55 Greg KH
2012-01-25 22:34 ` Greg KH
2012-06-22 19:04 ` Jiri Slaby
2012-06-22 19:38 ` Willy Tarreau
2012-06-22 19:38 ` Greg KH
2012-06-22 21:10 ` Jiri Slaby [this message]
2012-06-22 21:18 ` Willy Tarreau
2012-06-22 21:33 ` Jiri Slaby
2012-06-23 20:57 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FE4DF41.30400@suse.cz \
--to=jslaby@suse.cz \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox