From: Greg KH <gregkh@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: - <kd6lvw@yahoo.com>, linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [00/38] 2.6.35.1-stable review
Date: Fri, 6 Aug 2010 16:39:12 -0700 [thread overview]
Message-ID: <20100806233912.GA16793@suse.de> (raw)
In-Reply-To: <4C5C7AC8.9050307@zytor.com>
On Fri, Aug 06, 2010 at 02:12:40PM -0700, H. Peter Anvin wrote:
> On 08/06/2010 01:34 PM, Greg KH wrote:
> >On Fri, Aug 06, 2010 at 01:22:10PM -0700, - wrote:
> >>Does not include the fix to this bug (introduced in 2.6.35.0):
> >>
> >> https://bugzilla.kernel.org/show_bug.cgi?id=16506
> >>
> >>Affected file: arch/x86/lib/atomic64_386_32.S
> >>
> >>This issue causes a compile-time blocking failure. The patch fixes the problem for older versions of BINUTILS equal to or more recent than the minimum required version currently listed in file Documentation/Changes.
> >>
> >>Patch: https://bugzilla.kernel.org/attachment.cgi?id=27360
> >>
> >>Please include this in 2.6.35.1 and any other affected kernels.
> >>
> >>The problem was introduced on February 24 through March 1, 2010 by multiple commits, starting with commit a7e926abc3adfbd2e5e20d2b46177adb4e313915.
> >>
> >
> >Which exact patch that is in Linus's tree fixes the problem? Do you
> >have the git commit id of it? That's what I need here.
> >
>
> Not upstream just yet.
Ok, care to let stable@kernel.org know when it goes into Linus's tree?
thanks,
greg k-h
next prev parent reply other threads:[~2010-08-06 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <512689.43589.qm@web84207.mail.re3.yahoo.com>
2010-08-06 20:34 ` [00/38] 2.6.35.1-stable review Greg KH
2010-08-06 21:12 ` H. Peter Anvin
2010-08-06 23:39 ` Greg KH [this message]
2010-08-07 0:32 ` H. Peter Anvin
2010-08-06 18:32 Greg KH
2010-08-06 19:14 ` Thomas Backlund
2010-08-06 19:16 ` Greg KH
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=20100806233912.GA16793@suse.de \
--to=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=kd6lvw@yahoo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.