From: "H. Peter Anvin" <hpa@zytor.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Hans Rosenfeld <hans.rosenfeld@amd.com>,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
tglx@linutronix.de, robert.richter@amd.com,
andreas.herrmann3@amd.com
Subject: Re: [RFC] x86, fpu: unify signal handling code paths for x86 and x86_64 kernels
Date: Thu, 14 Jun 2012 18:17:47 -0700 [thread overview]
Message-ID: <4FDA8D3B.5020107@zytor.com> (raw)
In-Reply-To: <1339723004.3475.59.camel@sbsiddha-desk.sc.intel.com>
On 06/14/2012 06:16 PM, Suresh Siddha wrote:
> On Thu, 2012-06-14 at 18:13 -0700, H. Peter Anvin wrote:
>> On 06/14/2012 06:07 PM, Suresh Siddha wrote:
>>> Ok. Fix for the existing mainline code appended. Can you queue this
>>> separately?
>>
>> Your unification patch still needs this too, though, right?
>>
>
> Yes, that will be new code. Not for 3.5 though. So will send it
> separately, when I send the non-RFC version of the signal unification
> patches.
>
Thanks. Actually what would be better is to just base that patch on top
of tip:x86/urgent unless it is already merged into mainline by then.
-hpa
next prev parent reply other threads:[~2012-06-15 1:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 0:03 [RFC] x86, fpu: unify signal handling code paths for x86 and x86_64 kernels Suresh Siddha
2012-06-13 0:17 ` H. Peter Anvin
2012-06-14 14:37 ` Hans Rosenfeld
2012-06-14 20:45 ` Suresh Siddha
2012-06-15 0:10 ` Suresh Siddha
2012-06-15 0:16 ` H. Peter Anvin
2012-06-15 1:07 ` Suresh Siddha
2012-06-15 1:13 ` H. Peter Anvin
2012-06-15 1:16 ` Suresh Siddha
2012-06-15 1:17 ` H. Peter Anvin [this message]
2012-06-16 3:14 ` [tip:x86/urgent] x86, compat: Use test_thread_flag(TIF_IA32) in compat signal delivery tip-bot for Suresh Siddha
2012-06-14 20:48 ` [RFC] x86, fpu: unify signal handling code paths for x86 and x86_64 kernels H. Peter Anvin
2012-06-14 20:49 ` Suresh Siddha
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=4FDA8D3B.5020107@zytor.com \
--to=hpa@zytor.com \
--cc=andreas.herrmann3@amd.com \
--cc=hans.rosenfeld@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--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