From: Davidlohr Bueso <dbueso@suse.de>
To: paulmck@linux.vnet.ibm.com
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
bobby.prani@gmail.com, oleg@redhat.com,
ard.biesheuvel@linaro.org, joe@perches.com, rostedt@goodmis.org
Subject: Re: [GIT PULL rcu/next] RCU commits for 3.18
Date: Tue, 23 Sep 2014 09:46:32 +0200 [thread overview]
Message-ID: <1411458392.8304.2.camel@linux-t7sj.site> (raw)
In-Reply-To: <20140922214603.GA6356@linux.vnet.ibm.com>
Hi Paul,
On Mon, 2014-09-22 at 14:46 -0700, Paul E. McKenney wrote:
> 4. Torture-test updates. These were posted to LKML at
> https://lkml.org/lkml/2014/8/28/546 and at
> https://lkml.org/lkml/2014/9/11/1114.
I was planning on sending you another batch of torture patches. Would
you rather I hold off until the next merge window, or is it still ok to
send?
Thanks,
Davidlohr
next prev parent reply other threads:[~2014-09-23 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 21:46 [GIT PULL rcu/next] RCU commits for 3.18 Paul E. McKenney
2014-09-23 5:23 ` Ingo Molnar
2014-09-23 7:46 ` Davidlohr Bueso [this message]
2014-09-23 12:02 ` Paul E. McKenney
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=1411458392.8304.2.camel@linux-t7sj.site \
--to=dbueso@suse.de \
--cc=ard.biesheuvel@linaro.org \
--cc=bobby.prani@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.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