From: Chanwoo Choi <cwchoi00@gmail.com>
To: Ansuel Smith <ansuelsmth@gmail.com>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Sibi Sankar <sibis@codeaurora.org>,
Saravana Kannan <skannan@codeaurora.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 4/4] PM / devfreq: Mute warning on governor PROBE_DEFER
Date: Sat, 18 Jun 2022 03:09:30 +0900 [thread overview]
Message-ID: <fa35e955-41be-bb4b-d1f0-85acec03e0a0@gmail.com> (raw)
In-Reply-To: <62a9b027.1c69fb81.5ae2b.4f85@mx.google.com>
On 22. 6. 15. 18:22, Ansuel Smith wrote:
> On Wed, Jun 15, 2022 at 03:56:31PM +0900, Chanwoo Choi wrote:
>> On 22. 6. 15. 08:09, Christian 'Ansuel' Marangi wrote:
>>> Don't print warning when a governor PROBE_DEFER as it's not a real
>>> GOV_START fail.
>>>
>>> Fixes: a03dacb0316f ("PM / devfreq: Add cpu based scaling support to passive governor")
>>> Signed-off-by: Christian 'Ansuel' Marangi <ansuelsmth@gmail.com>
>>> ---
>>> drivers/devfreq/devfreq.c | 5 +++--
>>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
>>> index 2e2b3b414d67..6a39638ed064 100644
>>> --- a/drivers/devfreq/devfreq.c
>>> +++ b/drivers/devfreq/devfreq.c
>>> @@ -931,8 +931,9 @@ struct devfreq *devfreq_add_device(struct device *dev,
>>> err = devfreq->governor->event_handler(devfreq, DEVFREQ_GOV_START,
>>> NULL);
>>> if (err) {
>>> - dev_err(dev, "%s: Unable to start governor for the device\n",
>>> - __func__);
>>> + dev_err_probe(dev, err,
>>> + "%s: Unable to start governor for the device\n",
>>> + __func__);
>>> goto err_init;
>>> }
>>> create_sysfs_files(devfreq, devfreq->governor);
>>
>>
>> In order to keep the left-align with above error log
>> when try_then_request_governor() is failed,
>> I recommend to use the tab without space indentation as following:
>>
>> If you have no objection, I'll merge this change.
>>
>
> Sure, good for me. Anyway I wonder if we can relax the hard limit for 80
> for error print since we now can use 100, but your choice.
My suggestion is not over 80 line. Applied it.
>
>> diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
>> index 01474daf4548..80a1235ef8fb 100644
>> --- a/drivers/devfreq/devfreq.c
>> +++ b/drivers/devfreq/devfreq.c
>> @@ -932,8 +932,9 @@ struct devfreq *devfreq_add_device(struct device *dev,
>> err = devfreq->governor->event_handler(devfreq, DEVFREQ_GOV_START,
>> NULL);
>> if (err) {
>> - dev_err(dev, "%s: Unable to start governor for the device\n",
>> - __func__);
>> + dev_err_probe(dev, err,
>> + "%s: Unable to start governor for the device\n",
>> + __func__);
>> goto err_init;
>> }
>> create_sysfs_files(devfreq, devfreq->governor);
>>
>>
>>
>>
>>
>> --
>> Best Regards,
>> Samsung Electronics
>> Chanwoo Choi
>
--
Best Regards,
Samsung Electronics
Chanwoo Choi
prev parent reply other threads:[~2022-06-17 18:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 23:09 [PATCH v4 0/4] PM / devfreq: Various Fixes to cpufreq based passive governor Christian 'Ansuel' Marangi
2022-06-14 23:09 ` [PATCH v4 1/4] PM / devfreq: Fix cpufreq passive unregister erroring on PROBE_DEFER Christian 'Ansuel' Marangi
2022-06-15 6:48 ` Chanwoo Choi
2022-06-15 9:13 ` Ansuel Smith
2022-06-17 18:35 ` Chanwoo Choi
2022-06-14 23:09 ` [PATCH v4 2/4] PM / devfreq: Fix kernel warning with cpufreq passive register fail Christian 'Ansuel' Marangi
2022-06-15 7:11 ` Chanwoo Choi
2022-06-15 9:20 ` Ansuel Smith
2022-06-17 19:08 ` Chanwoo Choi
2022-06-19 22:19 ` Christian Marangi
2022-06-14 23:09 ` [PATCH v4 3/4] PM / devfreq: Rework freq_table to be local to devfreq struct Christian 'Ansuel' Marangi
2022-06-17 19:33 ` Chanwoo Choi
2022-06-17 19:38 ` Christian Marangi
2022-06-18 13:57 ` Chanwoo Choi
2022-06-14 23:09 ` [PATCH v4 4/4] PM / devfreq: Mute warning on governor PROBE_DEFER Christian 'Ansuel' Marangi
2022-06-15 6:56 ` Chanwoo Choi
2022-06-15 9:22 ` Ansuel Smith
2022-06-17 18:09 ` Chanwoo Choi [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=fa35e955-41be-bb4b-d1f0-85acec03e0a0@gmail.com \
--to=cwchoi00@gmail.com \
--cc=ansuelsmth@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sibis@codeaurora.org \
--cc=skannan@codeaurora.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