From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/3] percpu: remove PERCPU_ENOUGH_ROOM which is stale definition
Date: Tue, 3 Nov 2015 17:07:01 -0500 [thread overview]
Message-ID: <20151103220701.GC5749@mtj.duckdns.org> (raw)
In-Reply-To: <36E66A14-F5AE-45DA-A759-82F1BA5DFE98@gmail.com>
Hello,
On Tue, Nov 03, 2015 at 11:12:51PM +0900, Jungseok Lee wrote:
> On Nov 3, 2015, at 4:10 AM, Tejun Heo wrote:
>
> Dear Tejun,
>
> > On Sun, Nov 01, 2015 at 07:46:15AM +0000, Jungseok Lee wrote:
> >> As pure cleanup, this patch removes PERCPU_ENOUGH_ROOM which is not
> >> used any more. That is, no code refers to the definition.
> >>
> >> Signed-off-by: Jungseok Lee <jungseoklee85@gmail.com>
> >
> > Applied to percpu/for-4.4.
>
> Thanks for taking care of this!
Can you please refresh the patch so that it also drops
PERCPU_ENOUGH_ROOM definition from ia64?
Thanks.
--
tejun
next prev parent reply other threads:[~2015-11-03 22:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 7:46 [PATCH v6 0/3] Introduce IRQ stack on arm64 with percpu changes Jungseok Lee
2015-11-01 7:46 ` [PATCH v6 1/3] percpu: remove PERCPU_ENOUGH_ROOM which is stale definition Jungseok Lee
2015-11-02 16:08 ` Christoph Lameter
2015-11-02 19:10 ` Tejun Heo
2015-11-03 14:12 ` Jungseok Lee
2015-11-03 22:07 ` Tejun Heo [this message]
2015-11-04 13:19 ` Jungseok Lee
2015-11-01 7:46 ` [PATCH v6 2/3] percpu: add PERCPU_ATOM_SIZE for a generic percpu area setup Jungseok Lee
2015-11-02 16:10 ` Christoph Lameter
2015-11-02 16:22 ` Catalin Marinas
2015-11-02 16:48 ` Christoph Lameter
2015-11-02 17:35 ` Catalin Marinas
2015-11-02 18:11 ` Christoph Lameter
2015-11-02 18:31 ` Catalin Marinas
2015-11-03 13:49 ` Jungseok Lee
2015-11-03 17:58 ` James Morse
2015-11-04 13:35 ` Jungseok Lee
2015-11-03 14:11 ` Jungseok Lee
2015-11-01 7:46 ` [PATCH v6 3/3] arm64: Introduce IRQ stack Jungseok Lee
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=20151103220701.GC5749@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).