From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/3] Polish rcutorture.h
Date: Sun, 7 Aug 2016 11:25:22 -0700 [thread overview]
Message-ID: <20160807182522.GF3482@linux.vnet.ibm.com> (raw)
In-Reply-To: <1470541287-12588-1-git-send-email-sj38.park@gmail.com>
On Sun, Aug 07, 2016 at 12:41:24PM +0900, SeongJae Park wrote:
> This patchset contains few fixups for trivial nitpicks of rcutorture.
Good catches, applied and pushed.
Thanx, Paul
> SeongJae Park (3):
> rcutorture: Update usage
> rcutorture: Remove redundant n_read_pt initialization
> rcutorture: Protect fake workload from compiler optimization
>
> CodeSamples/defer/rcutorture.h | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> --
> 1.9.1
>
prev parent reply other threads:[~2016-08-07 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 3:41 [PATCH 0/3] Polish rcutorture.h SeongJae Park
2016-08-07 3:41 ` [PATCH 1/3] rcutorture: Update usage SeongJae Park
2016-08-07 3:41 ` [PATCH 2/3] rcutorture: Remove redundant n_read_pt initialization SeongJae Park
2016-08-07 3:41 ` [PATCH 3/3] rcutorture: Protect fake workload from compiler optimization SeongJae Park
2016-08-07 18:25 ` Paul E. McKenney [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=20160807182522.GF3482@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.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