public inbox for linux-kernel@vger.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, Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH 1/4] x86: signal_32.c: introduce signr_convert()
Date: Thu, 25 Sep 2008 09:59:07 -0700	[thread overview]
Message-ID: <48DBC35B.3050105@ct.jp.nec.com> (raw)
In-Reply-To: <20080925081420.GB30349@elte.hu>

Ingo Molnar wrote:
> applied your patches to tip/x86/signal:
> 
> 4694d23: x86: signal_32.c: introduce macro ia32_setup_frame and ia32_setup_rt_frame
> 455edbc: x86: signal: introduce helper macro is_ia32
> b94fd69: x86: signal_64.c: introduce helper function signr_convert()
> 8d8c13b: x86: signal_32.c: introduce signr_convert()
> 
> thanks! FYI, your other 13 x86 signal code unification commits and other 
> x86-signals enhancements passed testing just fine so far.

Hi, Ingo.
Thanks for that information and testing my patches!
It's very important to test patches.

thanks,
Hiroshi Shimamoto

      reply	other threads:[~2008-09-25 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25  2:10 [PATCH 1/4] x86: signal_32.c: introduce signr_convert() Hiroshi Shimamoto
2008-09-25  2:12 ` [PATCH 2/4] x86: signal_64.c: introduce helper function signr_convert() Hiroshi Shimamoto
2008-09-25  2:13 ` [PATCH 3/4] x86: signal: introduce helper macro is_ia32 Hiroshi Shimamoto
2008-09-25  2:13 ` [PATCH 4/4] x86: signal_32.c: introduce macro ia32_setup_frame and ia32_setup_rt_frame Hiroshi Shimamoto
2008-09-25  8:14 ` [PATCH 1/4] x86: signal_32.c: introduce signr_convert() Ingo Molnar
2008-09-25 16:59   ` 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=48DBC35B.3050105@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=roland@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox