linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org
Subject: Re: [RFC PATCH] arm: kconfig: push down CACHE_L2X0
Date: Mon, 12 Apr 2010 19:50:24 +0100	[thread overview]
Message-ID: <20100412185024.GH3048@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1270236996.26326.7.camel@c-dwalke-linux.qualcomm.com>

On Fri, Apr 02, 2010 at 12:36:36PM -0700, Daniel Walker wrote:
> Does it make sense to push down this value? It looks like it's just
> adding more and more sub-architectures .. Is the method below
> acceptable?

Yes, but please name it HAVE_CACHE_L2X0.

      reply	other threads:[~2010-04-12 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02 19:36 [RFC PATCH] arm: kconfig: push down CACHE_L2X0 Daniel Walker
2010-04-12 18:50 ` Russell King - ARM Linux [this message]

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=20100412185024.GH3048@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=dwalker@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.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 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).