From: Stephen Boyd <sboyd@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Russell King <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-next@vger.kernel.org,
Will Deacon <will.deacon@arm.com>,
Rob Clark <robdclark@gmail.com>
Subject: Re: [PATCH] ARM: vfp: Silence mvfr0 unused variable warning
Date: Tue, 18 Nov 2014 13:31:22 -0800 [thread overview]
Message-ID: <546BBAAA.4050909@codeaurora.org> (raw)
In-Reply-To: <20141119081438.3df66238@canb.auug.org.au>
On 11/18/2014 01:14 PM, Stephen Rothwell wrote:
> One small nit below:
>> + if (IS_ENABLED(CONFIG_VFPv3)) {
>> + mvfr0 = fmrx(MVFR0);
> Now that you have a block here, you could move the declaration of mvfr0
> into this block, right?
>
Sure I can squash in that change.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: vfp: Silence mvfr0 unused variable warning
Date: Tue, 18 Nov 2014 13:31:22 -0800 [thread overview]
Message-ID: <546BBAAA.4050909@codeaurora.org> (raw)
In-Reply-To: <20141119081438.3df66238@canb.auug.org.au>
On 11/18/2014 01:14 PM, Stephen Rothwell wrote:
> One small nit below:
>> + if (IS_ENABLED(CONFIG_VFPv3)) {
>> + mvfr0 = fmrx(MVFR0);
> Now that you have a block here, you could move the declaration of mvfr0
> into this block, right?
>
Sure I can squash in that change.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-11-18 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 20:56 [PATCH] ARM: vfp: Silence mvfr0 unused variable warning Stephen Boyd
2014-11-18 20:56 ` Stephen Boyd
2014-11-18 21:14 ` Stephen Rothwell
2014-11-18 21:14 ` Stephen Rothwell
2014-11-18 21:31 ` Stephen Boyd [this message]
2014-11-18 21:31 ` Stephen Boyd
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=546BBAAA.4050909@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robdclark@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.