From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: pl2x0/pl310: Refactor Kconfig to be more maintainable
Date: Wed, 30 Nov 2011 14:40:39 -0600 [thread overview]
Message-ID: <4ED694C7.6020502@gmail.com> (raw)
In-Reply-To: <1322675975-4471-1-git-send-email-dave.martin@linaro.org>
On 11/30/2011 11:59 AM, Dave Martin wrote:
> Making CACHE_L2X0 depends on (huge list of MACH_ and ARCH_ configs)
> is bothersome to maintain and likely to lead to merge conflicts.
>
> This patch moves the knowledge of which platforms have a L2x0 or
> PL310 cache controller to the individual machines. To enable this,
> a new HAVE_L2X0_L2CC config option is introduced to allow machines
> to indicate that they have such a cache controller independently of
> each other.
>
> Signed-off-by: Dave Martin <dave.martin@linaro.org>
> ---
> Changes since v1:
>
> v2: Add HAVE_L2X0_L2CC instead of CACHE_L2X0 for SOC_IMX6Q.
> (Thanks to Shawn Guo for suggesting this.)
>
Did you not see my comments on v1?
Rob
next prev parent reply other threads:[~2011-11-30 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 17:59 [PATCH v2] ARM: pl2x0/pl310: Refactor Kconfig to be more maintainable Dave Martin
2011-11-30 20:40 ` Rob Herring [this message]
2011-12-06 16:28 ` Dave Martin
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=4ED694C7.6020502@gmail.com \
--to=robherring2@gmail.com \
--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).