linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Avi Fishman <avifishman70@gmail.com>
Cc: Joel Stanley <joel@jms.id.au>, Tomer Maimon <tmaimon77@gmail.com>,
	Patrick Venture <venture@google.com>,
	Nancy Yuen <yuenn@google.com>,
	Brendan Higgins <brendanhiggins@google.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: npcm: drop extraneous 'select' statements
Date: Thu, 8 Mar 2018 11:51:45 +0100	[thread overview]
Message-ID: <CAK8P3a3fCRAuBjLXbjzc+1rYJsW90TDN2URZ=sOHvRNB3kyd6Q@mail.gmail.com> (raw)
In-Reply-To: <CAKKbWA5F29HJFOTNfVmt14Qg5rMgrLSsHjY4NQESZL6OKmA95w@mail.gmail.com>

On Thu, Mar 8, 2018 at 11:46 AM, Avi Fishman <avifishman70@gmail.com> wrote:
> So at least replace CACHE_L2X0 with MIGHT_HAVE_CACHE_L2X0 then
> CACHE_L2X0 will be selected by default and user can still remove it.

I looked at the other platforms for this one again, and found that most simply
select CONFIG_CACHE_L2X0 directly, so we probably want the same here
after all.

The ones that use MIGHT_HAVE_CACHE_L2X0 are the platforms
that have multiple SoCs in one family, and only some of them have an
L2X0. Is that the case here as well? Usually, the L2X0 is used with
Cortex-A9 and A5, rarely on older cores, and never on newer
ones.

       Arnd

  reply	other threads:[~2018-03-08 10:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 16:24 [PATCH 1/2] ARM: npcm: add CONFIG_ARCH_MULTI_V7 dependency Arnd Bergmann
2018-03-07 16:24 ` [PATCH 2/2] ARM: npcm: drop extraneous 'select' statements Arnd Bergmann
2018-03-08  2:12   ` Joel Stanley
2018-03-08 10:46     ` Avi Fishman
2018-03-08 10:51       ` Arnd Bergmann [this message]
2018-03-12 10:16   ` Tomer Maimon
2018-03-12 11:43     ` Tomer Maimon
2018-03-12 12:43       ` Arnd Bergmann
2018-03-09  2:08 ` [PATCH 1/2] ARM: npcm: add CONFIG_ARCH_MULTI_V7 dependency Brendan Higgins
2018-03-12 13:28   ` Tomer Maimon
2018-03-12 13:37     ` Arnd Bergmann
2018-03-12 15:15       ` Tomer Maimon
2018-03-13 13:35         ` Tomer Maimon
2018-03-13 16:23           ` Arnd Bergmann

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='CAK8P3a3fCRAuBjLXbjzc+1rYJsW90TDN2URZ=sOHvRNB3kyd6Q@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=avifishman70@gmail.com \
    --cc=brendanhiggins@google.com \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=tmaimon77@gmail.com \
    --cc=venture@google.com \
    --cc=yuenn@google.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).