From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: topology: Get rid of "cap_parsing_done"
Date: Wed, 21 Jun 2017 09:04:26 +0530 [thread overview]
Message-ID: <20170621033426.GP3942@vireshk-i7> (raw)
In-Reply-To: <20170620155400.GI21131@arm.com>
On 20-06-17, 16:54, Will Deacon wrote:
> On Tue, Jun 20, 2017 at 04:14:40PM +0530, Viresh Kumar wrote:
> > We can reuse "cap_parsing_failed" instead of keeping an additional
> > variable. Also rename cap_parsing_failed to skip_cap_parsing.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> > arch/arm64/kernel/topology.c | 19 +++++++++----------
> > 1 file changed, 9 insertions(+), 10 deletions(-)
>
> You probably need to co-ordinate with this series:
>
> http://lkml.kernel.org/r/20170531165931.6945-5-juri.lelli at arm.com
>
> and it would be clearer to split up the renaming part of the patch from the
> remove of the additional bool.
Thanks, I missed that series for sure :)
--
viresh
prev parent reply other threads:[~2017-06-21 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 10:44 [PATCH] arm64: topology: Get rid of "cap_parsing_done" Viresh Kumar
2017-06-20 15:54 ` Will Deacon
2017-06-21 3:34 ` Viresh Kumar [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=20170621033426.GP3942@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--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