From: Tejun Heo <tj@kernel.org>
To: Cao jin <caoj.fnst@cn.fujitsu.com>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
arnd@arndb.de, cl@linux.com
Subject: Re: [PATCH] percpu: drop useless macro PER_CPU_DEF_ATTRIBUTES
Date: Tue, 28 Mar 2017 12:00:40 -0400 [thread overview]
Message-ID: <20170328160040.GC28157@htj.duckdns.org> (raw)
In-Reply-To: <1490690107-30009-1-git-send-email-caoj.fnst@cn.fujitsu.com>
On Tue, Mar 28, 2017 at 04:35:07PM +0800, Cao jin wrote:
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
I'm not sure. I think I used it during development and it's not like
it costs anything to keep.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-03-28 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 8:35 [PATCH] percpu: drop useless macro PER_CPU_DEF_ATTRIBUTES Cao jin
2017-03-28 16:00 ` Tejun Heo [this message]
2017-03-29 2:38 ` Cao jin
2017-03-29 15:28 ` Tejun Heo
2017-03-29 15:28 ` Tejun Heo
2017-03-30 3:34 ` Cao jin
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=20170328160040.GC28157@htj.duckdns.org \
--to=tj@kernel.org \
--cc=arnd@arndb.de \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=cl@linux.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).