From: wangkefeng.wang@huawei.com (Kefeng Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: l2x0: fix build warning without CONFIG_OF
Date: Fri, 1 Aug 2014 16:57:35 +0800 [thread overview]
Message-ID: <53DB567F.2070400@huawei.com> (raw)
In-Reply-To: <20140801075843.GO30282@n2100.arm.linux.org.uk>
On 08/01 15:58, Russell King - ARM Linux wrote:
> On Fri, Aug 01, 2014 at 10:42:00AM +0800, Kefeng Wang wrote:
>> Commit cf9ea8f13(ARM: l2c: remove obsolete l2x0 ops for non-OF init)
>> remove some obsolete l2x0 ops, the rest of ops: l2x0_cache_sync,
>> l2x0_cache_sync, l2x0_disable only use under OF enable, so move them
>> into OF part, or "defined but not used" warning occurs.
>
> I'm not interested; I've stated previously that I want these warnings
> to stay until such time that the code which uses them is fixed up to
> use the new methods.
>
> The warnings act as an advertisment that it needs fixing properly.
>
Ok, ignore pls.
prev parent reply other threads:[~2014-08-01 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 2:42 [PATCH] ARM: l2x0: fix build warning without CONFIG_OF Kefeng Wang
2014-08-01 7:58 ` Russell King - ARM Linux
2014-08-01 8:57 ` Kefeng Wang [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=53DB567F.2070400@huawei.com \
--to=wangkefeng.wang@huawei.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).