From: James Hogan <james.hogan@imgtec.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Mundt <lethal@linux-sh.org>,
Paul Mackerras <paulus@samba.org>, Tejun Heo <tj@kernel.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] memblock: kill "config MAX_ACTIVE_REGIONS"
Date: Thu, 21 Mar 2013 09:48:29 +0000 [thread overview]
Message-ID: <514AD76D.2020401@imgtec.com> (raw)
In-Reply-To: <20130321093455.GA8027@linux-sh.org>
On 21/03/13 09:34, Paul Mundt wrote:
> On Thu, Mar 21, 2013 at 10:27:56AM +0100, Paul Bolle wrote:
>> The Kconfig symbol MAX_ACTIVE_REGIONS is unused. Commit
>> 0ee332c1451869963626bf9cac88f165a90990e1 ("memblock: Kill
>> early_node_map[]") removed the only place were it was actually used. But
>> it did not remove its Kconfig entries (for powerpc and sh).
>>
>> Remove those two entries (and the entry for metag, that popped up in
>> v3.9-rc1).
>>
>> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
>> ---
>> 0) Eyeball tested again.
>>
>> 1) It felt silly to split this clean up patch into three patches. But if
>> the maintainers involved disagree I'm happy to split and resend it.
>>
> Given that it's unused now it doesn't really matter how it gets applied,
> it looks fine to me.
>
> Acked-by: Paul Mundt <lethal@linux-sh.org>
>
Acked-by: James Hogan <james.hogan@imgtec.com>
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Paul Mundt <lethal@linux-sh.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>, Tejun Heo <tj@kernel.org>,
<linuxppc-dev@lists.ozlabs.org>, <linux-sh@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] memblock: kill "config MAX_ACTIVE_REGIONS"
Date: Thu, 21 Mar 2013 09:48:29 +0000 [thread overview]
Message-ID: <514AD76D.2020401@imgtec.com> (raw)
In-Reply-To: <20130321093455.GA8027@linux-sh.org>
On 21/03/13 09:34, Paul Mundt wrote:
> On Thu, Mar 21, 2013 at 10:27:56AM +0100, Paul Bolle wrote:
>> The Kconfig symbol MAX_ACTIVE_REGIONS is unused. Commit
>> 0ee332c1451869963626bf9cac88f165a90990e1 ("memblock: Kill
>> early_node_map[]") removed the only place were it was actually used. But
>> it did not remove its Kconfig entries (for powerpc and sh).
>>
>> Remove those two entries (and the entry for metag, that popped up in
>> v3.9-rc1).
>>
>> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
>> ---
>> 0) Eyeball tested again.
>>
>> 1) It felt silly to split this clean up patch into three patches. But if
>> the maintainers involved disagree I'm happy to split and resend it.
>>
> Given that it's unused now it doesn't really matter how it gets applied,
> it looks fine to me.
>
> Acked-by: Paul Mundt <lethal@linux-sh.org>
>
Acked-by: James Hogan <james.hogan@imgtec.com>
next prev parent reply other threads:[~2013-03-21 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 9:27 [PATCH] memblock: kill "config MAX_ACTIVE_REGIONS" Paul Bolle
2013-03-21 9:27 ` Paul Bolle
2013-03-21 9:27 ` Paul Bolle
2013-03-21 9:34 ` Paul Mundt
2013-03-21 9:34 ` Paul Mundt
2013-03-21 9:34 ` Paul Mundt
2013-03-21 9:48 ` James Hogan [this message]
2013-03-21 9:48 ` James Hogan
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=514AD76D.2020401@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=pebolle@tiscali.nl \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.