From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Minjie Du <duminjie@vivo.com>
Cc: Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
opensource.kernel@vivo.com
Subject: Re: [PATCH v1] thermal/debugfs: Remove unnecessary debugfs_create_dir() error check in thermal_debug_init()
Date: Mon, 15 Jan 2024 17:55:02 +0100 [thread overview]
Message-ID: <ecb33c61-bb40-43a0-94a1-8973d70dc0b4@linaro.org> (raw)
In-Reply-To: <CAJZ5v0jPeYgGc9xmSrnLsg6RkhzmU=TfPdhrzxWBd_d_dmJh+Q@mail.gmail.com>
On 15/01/2024 16:52, Rafael J. Wysocki wrote:
> On Mon, Jan 15, 2024 at 9:25 AM Minjie Du <duminjie@vivo.com> wrote:
>>
>> This patch removes the debugfs_create_dir() error checking in
>> thermal_debug_init(). Because the debugfs_create_dir() is developed
>> in a way that the caller can safely handle the errors that
>> occur during the creation of DebugFS nodes.
>
> I honestly don't see what the purpose of this patch is.
I think it is because the recent debugfs changes were about to reduce as
much as possible the code related to the error handling as the debugfs
is not supposed to go in production system.
So for instance debugfs_create_dir() will not fail if the parent is NULL
and will create the entry in the debugfs topdir.
At the end we are ending up with:
d_root = debugfs_create_dir("thermal", NULL);
d_cdev = debugfs_create_dir("cooling_devices", d_root);
d_tz = debugfs_create_dir("thermal_zones", d_root);
The current code will avoid creating lost entries in /sys/kernel/debug
The proposed change will create those in /sys/kernel/debug in case of error.
Note I reduced as much as possible the error handling in this function.
So it is a matter to reduce it even more but may be resulting in junk in
/sys/kernel/debug in case of error
TBH, I'm 50/50 :)
>> Signed-off-by: Minjie Du <duminjie@vivo.com>
>> ---
>> drivers/thermal/thermal_debugfs.c | 4 ----
>> 1 file changed, 4 deletions(-)
>>
>> diff --git a/drivers/thermal/thermal_debugfs.c b/drivers/thermal/thermal_debugfs.c
>> index a3fa09235da1..695253559a61 100644
>> --- a/drivers/thermal/thermal_debugfs.c
>> +++ b/drivers/thermal/thermal_debugfs.c
>> @@ -172,12 +172,8 @@ struct thermal_debugfs {
>> void thermal_debug_init(void)
>> {
>> d_root = debugfs_create_dir("thermal", NULL);
>> - if (!d_root)
>> - return;
>>
>> d_cdev = debugfs_create_dir("cooling_devices", d_root);
>> - if (!d_cdev)
>> - return;
>>
>> d_tz = debugfs_create_dir("thermal_zones", d_root);
>> }
>> --
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2024-01-15 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 8:25 Minjie Du
2024-01-15 15:52 ` Rafael J. Wysocki
2024-01-15 16:55 ` Daniel Lezcano [this message]
2024-01-15 17:09 ` Rafael J. Wysocki
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=ecb33c61-bb40-43a0-94a1-8973d70dc0b4@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=duminjie@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=opensource.kernel@vivo.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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
all inboxes | Powered by JetHome®