From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Will Deacon <will.deacon@arm.com>,
Rob Clark <robdclark@gmail.com>
Subject: Re: linux-next: build warning after merge of the arm tree
Date: Tue, 18 Nov 2014 19:21:03 +0000 [thread overview]
Message-ID: <20141118192103.GF4042@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <546B9696.4030703@codeaurora.org>
On Tue, Nov 18, 2014 at 10:57:26AM -0800, Stephen Boyd wrote:
> Urgh, I thought I fixed that but I guess I only took care of not
> assigning it unless we actually need it. Well we can do the #ifdef
> thing, or move to IS_ENABLED. Here's both options.
I'd prefer the first as it increases compiler coverage.
Thanks.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-11-18 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 8:25 linux-next: build warning after merge of the arm tree Stephen Rothwell
2014-11-18 18:57 ` Stephen Boyd
2014-11-18 19:21 ` Russell King - ARM Linux [this message]
2014-11-18 19:43 ` Stephen Boyd
-- strict thread matches above, loose matches on Subject: below --
2017-11-28 23:16 Stephen Rothwell
2017-11-28 23:19 ` Russell King
2017-11-28 23:38 ` Stephen Rothwell
2017-11-28 23:41 ` Russell King
2017-11-29 6:58 ` Nicolas Pitre
2017-11-28 23:31 ` Russell King
2017-11-28 23:38 ` Nicolas Pitre
2014-04-22 0:32 Stephen Rothwell
2014-04-22 0:59 ` Sebastian Capella
2014-04-22 8:35 ` Russell King - ARM Linux
2014-04-23 16:43 ` Sebastian Capella
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=20141118192103.GF4042@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sboyd@codeaurora.org \
--cc=sfr@canb.auug.org.au \
--cc=will.deacon@arm.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).