From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH 3/4] cleanup __exit_signal()
Date: Fri, 24 Feb 2006 16:20:29 -0800 [thread overview]
Message-ID: <20060225002029.GI1296@us.ibm.com> (raw)
In-Reply-To: <43FF4CC2.3BEED999@tv-sign.ru>
On Fri, Feb 24, 2006 at 09:13:22PM +0300, Oleg Nesterov wrote:
> "Paul E. McKenney" wrote:
> >
> > On Mon, Feb 20, 2006 at 07:04:03PM +0300, Oleg Nesterov wrote:
> > > This patch factors out duplicated code under 'if' branches.
> > > Also, BUG_ON() conversions and whitespace cleanups.
> >
> > Passed steamroller. Looks sane to me.
>
> Oh, thanks!
>
> I forgot to say it, but I had run steamroller tests too before I
> sent "some tasklist_lock removals" series.
Glad to hear it!
> Do you know any other test which may be useful too?
Matt Wilcox mentioned that a full build of gdb ran some tests that do
a good job of exercising signals. I have not yet tried this myself
(but am giving it a shot).
Also, my guess is that you ran steamroller on x86 (how many CPUs?).
I ran on ppc64.
Thanx, Paul
next prev parent reply other threads:[~2006-02-25 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 16:04 [PATCH 3/4] cleanup __exit_signal() Oleg Nesterov
2006-02-24 18:01 ` Paul E. McKenney
2006-02-24 18:13 ` Oleg Nesterov
2006-02-25 0:20 ` Paul E. McKenney [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-25 1:48 Suzanne Wood
2006-02-25 19:26 ` Oleg Nesterov
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=20060225002029.GI1296@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.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 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.