From: Tejun Heo <htejun@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: David Miller <davem@davemloft.net>,
NetDev <netdev@vger.kernel.org>, Shan Wei <shanwei88@gmail.com>,
Kernel-Maillist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/9 v4] use efficient this_cpu_* helper
Date: Thu, 15 Nov 2012 06:53:25 -0800 [thread overview]
Message-ID: <20121115145325.GC7306@mtj.dyndns.org> (raw)
In-Reply-To: <0000013b047079ab-01971b64-07e2-4f2e-a204-6baff2180fc3-000000@email.amazonses.com>
On Thu, Nov 15, 2012 at 02:19:38PM +0000, Christoph Lameter wrote:
> Tejon: Could you pick up this patchset?
Sure, but, Shan, when posting patchset, please make the patches
replies to the head message; otherwise, it's pretty difficult to track
what's going on with the patchset as a whole. I see that some patches
are being picked up by respective subsystems. If you have patches
left, please let me know.
Thanks.
--
tejun
next prev parent reply other threads:[~2012-11-15 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 1:51 [PATCH 0/9 v4] use efficient this_cpu_* helper Shan Wei
2012-11-15 14:19 ` Christoph Lameter
2012-11-15 14:53 ` Tejun Heo [this message]
2012-11-16 8:30 ` Shan Wei
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=20121115145325.GC7306@mtj.dyndns.org \
--to=htejun@gmail.com \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shanwei88@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;
as well as URLs for NNTP newsgroup(s).