From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Michal Simek <michal.simek@petalogix.com>,
LKML <linux-kernel@vger.kernel.org>,
hpa@zytor.com, John Williams <john.williams@petalogix.com>
Subject: Re: Split 'flush_old_exec' into two functions - 221af7f87b97431e3ee21ce4b0e77d5411cf1549
Date: Mon, 1 Feb 2010 10:41:43 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1002011036540.4206@localhost.localdomain> (raw)
In-Reply-To: <4B671865.5030705@windriver.com>
On Mon, 1 Feb 2010, Jason Wessel wrote:
>
> Add to the afflicted architecture list a ppc64 kernel running 32 bit
> user space apps such as a dynamically linked busybox:
The ppc issue was known - I informed the ppc people before committing, as
they were actually using the same insane trick (along with sparc) that x86
had to work around the bad calling conventions.
So x86, sparc and ppc were actually the main targets of the cleanup, the
powerpc patch just wasn't ready in time. But it's merged now (got a pull
request today), so powerpc should be ok now too (commit 94f28da84:
"powerpc: TIF_ABI_PENDING bit removal").
The microblaze thing is different, exactly because microblaze does _not_
have any of that insane 32-vs-64-bit executable fiddling that this cleanup
was all about. So microblaze I'd have expected to be totally unaffected,
and must be about something else.
Linus
next prev parent reply other threads:[~2010-02-01 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 14:00 Michal Simek
2010-02-01 15:57 ` Linus Torvalds
2010-02-01 18:07 ` Jason Wessel
2010-02-01 18:41 ` H. Peter Anvin
2010-02-01 18:41 ` Linus Torvalds [this message]
2010-02-01 18:56 ` Jason Wessel
2010-02-01 19:32 ` H. Peter Anvin
2010-02-02 10:14 ` Michal Simek
2010-02-02 10:16 ` Michal Simek
2010-02-02 15:50 ` Linus Torvalds
2010-02-02 19:52 ` Michal Simek
2010-02-02 21:45 ` 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=alpine.LFD.2.00.1002011036540.4206@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jason.wessel@windriver.com \
--cc=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@petalogix.com \
/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
all inboxes | Powered by JetHome®