From: Michal Marek <mmarek@suse.cz>
To: Greg KH <greg@kroah.com>
Cc: stable@kernel.org, Alan <alan@clueserver.org>,
linux-kernel@vger.kernel.org, "Krzysztof Hałasa" <khc@pm.waw.pl>
Subject: Re: [stable] [PATCH for stable] kbuild: Fix modpost segfault
Date: Tue, 29 Jun 2010 15:33:14 +0200 [thread overview]
Message-ID: <4C29F61A.2090905@suse.cz> (raw)
In-Reply-To: <20100629125422.GB29243@kroah.com>
On 29.6.2010 14:54, Greg KH wrote:
> On Tue, Jun 29, 2010 at 11:43:42AM +0200, Michal Marek wrote:
>> Hi Greg,
>>
>> please add this to stable, it's a bug that started showing up with newer
>> gcc. The upstream commit is 1c938663d58b5b2965976a6f54cc51b5d6f691aa.
>
> What -stable kernels do you want it applied to? .27, .32, .33, and/or
> .34?
I'd say all of them. I just tried it and applies cleanly.
Michal
next prev parent reply other threads:[~2010-06-29 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 9:43 [PATCH for stable] kbuild: Fix modpost segfault Michal Marek
2010-06-29 12:54 ` [stable] " Greg KH
2010-06-29 13:33 ` Michal Marek [this message]
2010-06-29 13:39 ` Greg KH
2010-06-29 22:35 ` Alan
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=4C29F61A.2090905@suse.cz \
--to=mmarek@suse.cz \
--cc=alan@clueserver.org \
--cc=greg@kroah.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
/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