From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Add ARCH_HAS_L2X0 and make CACHE_L2X0 config depend on that
Date: Wed, 16 Jun 2010 11:43:29 +0800 [thread overview]
Message-ID: <AANLkTimH979ASCut4dEE0FGJ-3PA3jzfHg_SzVM6eor_@mail.gmail.com> (raw)
In-Reply-To: <20100614145956.GA29355@lixom.net>
On Mon, Jun 14, 2010 at 10:59 PM, Olof Johansson <olof@lixom.net> wrote:
> On Sun, Jun 13, 2010 at 06:16:26AM +0100, Ben Dooks wrote:
>> On Fri, Jun 11, 2010 at 10:58:07AM -0700, Daniel Walker wrote:
>> >
>> > I made a similar change not too long ago, but Russell wanted the define
>> > to be HAVE_CACHE_L2X0 ..
>>
>> possibly, I was thinking ARM_L2X0 would also be an option, since if I
>> remeber correctly it is selecting the driver not the availability of
>> it.
>
> Yeah, there are lots of different possible names. :)
>
> Let's just go with the one Russell preferred and not worry too much
> about it. There's some presendence to using HAVE_.* already.
>
Sometimes I am thinking that maybe ARCH_HAS_* has some benefits:
HAVE_* for those kernel-wide and general capabilities
ARCH_HAS_* for those ARM machine-class specific capabilities?
So to make things a bit more clear? If ARCH_HAS_* is widely adopted
on architectures other than ARM, maybe we can then switch that name
to HAVE_*?
next prev parent reply other threads:[~2010-06-16 3:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6fqujhaev78923q90va>
2010-06-11 16:03 ` [PATCH] ARM: Add ARCH_HAS_L2X0 and make CACHE_L2X0 config depend on that Olof Johansson
2010-06-11 17:58 ` Daniel Walker
2010-06-12 4:13 ` [PATCH v2] ARM: Add HAVE_CACHE_L2X0 Olof Johansson
2010-06-13 5:16 ` [PATCH] ARM: Add ARCH_HAS_L2X0 and make CACHE_L2X0 config depend on that Ben Dooks
2010-06-14 14:59 ` Olof Johansson
2010-06-16 3:43 ` Eric Miao [this message]
2010-06-16 14:13 ` Olof Johansson
2010-06-16 14:22 ` Eric Miao
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=AANLkTimH979ASCut4dEE0FGJ-3PA3jzfHg_SzVM6eor_@mail.gmail.com \
--to=eric.y.miao@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).