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 11:52:37 -0700 [thread overview]
Message-ID: <4FB69A75.30507@zytor.com> (raw)
In-Reply-To: <20120518184121.GA3371@kroah.com>
On 05/18/2012 11:41 AM, Greg KH wrote:
> On Fri, May 18, 2012 at 09:51:44AM -0700, H. Peter Anvin wrote:
>> On 05/18/2012 09:50 AM, H.J. Lu wrote:
>>>
>>> A small testcase:
>>>
>>
>> Right, but we can equally well just let the postprocessing tool throw an
>> error.
>
> That would probably be the best thing to do right now, and we can
> backport that to the stable kernel releases also to ensure they work
> properly.
>
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)?
-hpa
next prev parent reply other threads:[~2012-05-18 18:52 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 [this message]
2012-05-18 19:11 ` Greg KH
2012-05-18 19:13 ` H. Peter Anvin
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=4FB69A75.30507@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox