All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] x86: signal: unify signal_{32|64}.c
Date: Wed, 26 Nov 2008 16:16:52 -0800	[thread overview]
Message-ID: <492DE6F4.3060300@ct.jp.nec.com> (raw)
In-Reply-To: <20081126041438.GB9732@elte.hu>

Ingo Molnar wrote:
> * Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> wrote:
> 
>> From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>>
>> Impact: cleanup
>>
>> Add #ifdef directive for 32-bit only code and unify signal_{32|64}.c
>>
>> Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>> ---
>>  arch/x86/kernel/Makefile    |    2 +-
>>  arch/x86/kernel/signal.c    |  915 +++++++++++++++++++++++++++++++++++++++++++
>>  arch/x86/kernel/signal_32.c |  909 ------------------------------------------
>>  arch/x86/kernel/signal_64.c |  801 -------------------------------------
>>  4 files changed, 916 insertions(+), 1711 deletions(-)
>>  create mode 100644 arch/x86/kernel/signal.c
>>  delete mode 100644 arch/x86/kernel/signal_32.c
>>  delete mode 100644 arch/x86/kernel/signal_64.c
> 
> yay! :-)
> 
> applied to tip/x86/signal, thanks Hiroshi!
> 
> One small detail, i inserted yet another commit in the middle:
> 
>  5ceb40d: x86: signal: unify signal_{32|64}.c
>  e5fa2d0: x86: signal: unify signal_{32|64}.c, prepare
>  bfeb91a: x86: signal: cosmetic unification of __setup_sigframe() and __setup_rt_sigframe()
>  2601657: x86: signal: move {setup|restore}_sigcontext()
> 
> the e5fa2d0 commit (see it below) contains all the non-mechanic 
> modifications that you did in the final unification commit. It's best 
> to keep this separate - because a big unification commit is hard to 
> review and debug, should it cause any problems.

Hi Ingo,

thanks for the above change, I think I was in a hurry because of
Thanksgiving Day week.

thanks,
Hiroshi Shimamoto

      reply	other threads:[~2008-11-27  0:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  2:21 [PATCH 1/3] x86: signal: move {setup|restore}_sigcontext() Hiroshi Shimamoto
2008-11-25  2:23 ` [PATCH 2/3] x86: signal: cosmetic unification of __setup_sigframe() and __setup_rt_sigframe() Hiroshi Shimamoto
2008-11-25  2:24 ` [PATCH 3/3] x86: signal: unify signal_{32|64}.c Hiroshi Shimamoto
2008-11-26  4:14   ` Ingo Molnar
2008-11-27  0:16     ` Hiroshi Shimamoto [this message]

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=492DE6F4.3060300@ct.jp.nec.com \
    --to=h-shimamoto@ct.jp.nec.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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.