From: "Agrawal, Akshu" <aagrawal2@amd.com>
To: Stephen Boyd <sboyd@kernel.org>, akshu.agrawal@amd.com
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [v2 4/4] clk: x86: Support RV architecture
Date: Tue, 28 Jul 2020 12:06:54 +0530 [thread overview]
Message-ID: <807b3eec-cc11-dbbf-7d35-0086df12f52b@amd.com> (raw)
In-Reply-To: <159531874995.3847286.4010361856630371541@swboyd.mtv.corp.google.com>
On 7/21/2020 1:35 PM, Stephen Boyd wrote:
> Quoting Akshu Agrawal (2020-07-19 22:04:59)
>> diff --git a/drivers/clk/x86/clk-fch.c b/drivers/clk/x86/clk-fch.c
>> index b252f0cf0628..d68bca7b213f 100644
>> --- a/drivers/clk/x86/clk-fch.c
>> +++ b/drivers/clk/x86/clk-fch.c
> [...]
>>
>> static int fch_clk_remove(struct platform_device *pdev)
>> {
>> - int i;
>> + int i, clks;
>> + struct fch_clk_data *fch_data;
>>
>> - for (i = 0; i < ST_MAX_CLKS; i++)
>> + fch_data = dev_get_platdata(&pdev->dev);
>> +
>> + clks = (!fch_data->is_rv) ? ST_MAX_CLKS : RV_MAX_CLKS;
> Useless parenthesis and negation, just write:
>
> num = fch_data->is_rv ? RV_MAX_CLKS : ST_MAX_CLKS;
Sure, including in the next patch set.
Thanks,
Akshu
>
>> +
>> + for (i = 0; i < clks; i++)
>> clk_hw_unregister(hws[i]);
>> +
>> return 0;
>> }
>>
prev parent reply other threads:[~2020-07-28 6:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200720050500.23357-1-akshu.agrawal@amd.com>
2020-07-20 5:04 ` [PATCH 1/4] ACPI: APD: Change name from ST to FCH Akshu Agrawal
2020-07-27 13:28 ` Rafael J. Wysocki
2020-07-28 5:50 ` Agrawal, Akshu
2020-07-28 11:17 ` Rafael J. Wysocki
2020-07-20 5:04 ` [PATCH 2/4] clk: x86: " Akshu Agrawal
2020-07-21 8:06 ` Stephen Boyd
2020-07-28 6:35 ` Agrawal, Akshu
2020-07-20 5:04 ` [PATCH 3/4] ACPI: APD: Add a fmw property is_raven Akshu Agrawal
2020-07-20 5:04 ` [v2 4/4] clk: x86: Support RV architecture Akshu Agrawal
2020-07-21 8:05 ` Stephen Boyd
2020-07-28 6:36 ` Agrawal, Akshu [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=807b3eec-cc11-dbbf-7d35-0086df12f52b@amd.com \
--to=aagrawal2@amd.com \
--cc=akshu.agrawal@amd.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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
all inboxes | Powered by JetHome®