From: Guenter Roeck <linux@roeck-us.net>
To: Osama Muhammad <osmtendev@gmail.com>
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ucd9000.c: Drop error checking for debugfs_create_dir
Date: Thu, 25 May 2023 11:20:58 -0700 [thread overview]
Message-ID: <efe65d37-0e15-4685-b071-5ddf2b07c6ef@roeck-us.net> (raw)
In-Reply-To: <20230525161313.15745-1-osmtendev@gmail.com>
On Thu, May 25, 2023 at 09:13:13PM +0500, Osama Muhammad wrote:
> This patch fixes the error checking in ucd9000.c.
Sure, but you should also explain what is wrong with the code
(i.e., that debugfs_create_dir() does not return NULL but an ERR_PTR
after an error).
> The DebugFS kernel API is developed in
> a way that the caller can safely ignore the errors that
> occur during the creation of DebugFS nodes.
>
If you plan t send more patches, please watch out for the subject line
to match subject lines used in a subsystem. Here it should start with
something like
hwmon: (pmbus/ucd9000) ...
Thanks,
Guenter
> Signed-off-by: Osama Muhammad <osmtendev@gmail.com>
> ---
> drivers/hwmon/pmbus/ucd9000.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/hwmon/pmbus/ucd9000.c b/drivers/hwmon/pmbus/ucd9000.c
> index 3daaf2237832..73559afa8ba7 100644
> --- a/drivers/hwmon/pmbus/ucd9000.c
> +++ b/drivers/hwmon/pmbus/ucd9000.c
> @@ -512,8 +512,6 @@ static int ucd9000_init_debugfs(struct i2c_client *client,
> return -ENOENT;
>
> data->debugfs = debugfs_create_dir(client->name, debugfs);
> - if (!data->debugfs)
> - return -ENOENT;
>
> /*
> * Of the chips this driver supports, only the UCD9090, UCD90160,
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-05-25 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 16:13 Osama Muhammad
2023-05-25 18:20 ` Guenter Roeck [this message]
[not found] ` <CAK6rUAObC7_r1Riqfr7nd_B1BKx=abGXYk7F+5euGCiB2+xmWg@mail.gmail.com>
2023-05-25 19:57 ` Guenter Roeck
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=efe65d37-0e15-4685-b071-5ddf2b07c6ef@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osmtendev@gmail.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®