From: "H. Peter Anvin" <hpa@zytor.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jarkko Sakkinen <jarkko.sakkinen@intel.com>
Subject: Re: Urgent: x86-32 and GNU ld 2.22.52.0.1
Date: Fri, 18 May 2012 12:13:30 -0700 [thread overview]
Message-ID: <4FB69F5A.2060808@zytor.com> (raw)
In-Reply-To: <20120518191103.GA11715@kroah.com>
On 05/18/2012 12:11 PM, Greg KH wrote:
>>
>> So the question is: do you want to simply take the patches from the
>> trampoline branch (which are reasonably tested) or do a minimal backport
>> which only throws an error (which would not be)?
>
> All 4 of those patches? They look simple and "sane" to me. They solve
> the problem even with the "buggy" binutils, right? If so, sure, I'll
> take those after they land in Linus's tree, which I'm guessing will be
> for 3.5-rc1, right?
>
We think they fix the problem even with the buggy binutils... and will
throw an error if they don't. I intend to push them for 3.5-rc1, but
Linus may want something for 3.4.
-hpa
next prev parent reply other threads:[~2012-05-18 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 15:56 Urgent: x86-32 and GNU ld 2.22.52.0.1 H. Peter Anvin
2012-05-18 16:11 ` H. Peter Anvin
2012-05-18 16:14 ` H.J. Lu
2012-05-18 16:16 ` H.J. Lu
2012-05-18 16:19 ` H. Peter Anvin
2012-05-18 16:35 ` H.J. Lu
2012-05-18 16:46 ` H. Peter Anvin
2012-05-18 16:50 ` H.J. Lu
2012-05-18 16:51 ` H. Peter Anvin
2012-05-18 18:41 ` Greg KH
2012-05-18 18:52 ` H. Peter Anvin
2012-05-18 19:11 ` Greg KH
2012-05-18 19:13 ` H. Peter Anvin [this message]
2012-05-18 16:20 ` H. Peter Anvin
2012-05-18 16:55 ` Josh Boyer
2012-05-19 10:20 ` Ingo Molnar
2012-05-19 18:12 ` H. Peter Anvin
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=4FB69F5A.2060808@zytor.com \
--to=hpa@zytor.com \
--cc=gregkh@linuxfoundation.org \
--cc=hjl.tools@gmail.com \
--cc=jarkko.sakkinen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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.