From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Yang Ruibin <11162571@vivo.com>
Cc: Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
"Andy Whitcroft" <apw@canonical.com>,
Joe Perches <joe@perches.com>,
"Dwaipayan Ray" <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Ingo Molnar <mingo@kernel.org>, <linux-edac@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <opensource.kernel@vivo.com>
Subject: Re: [PATCH v2] drivers:block:Use IS_ERR() to check debugfs_create_dir() return value
Date: Fri, 23 Aug 2024 09:29:59 +0100 [thread overview]
Message-ID: <20240823092959.00000c90@Huawei.com> (raw)
In-Reply-To: <20240822132358.2416027-1-11162571@vivo.com>
On Thu, 22 Aug 2024 21:23:58 +0800
Yang Ruibin <11162571@vivo.com> wrote:
Patch title needs an update as this isn't in block and that's not the
style used for this subsystem.
Otherwise fine.
> The debugfs_create_dir() function returns error pointers.It
> never returns NULL. So use IS_ERR() to check its return value.
>
> Fixes: 011d82611172 ("RAS: Add a Corrected Errors Collector")
> Signed-off-by: Yang Ruibin <11162571@vivo.com>
> ---
> drivers/ras/cec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/ras/cec.c b/drivers/ras/cec.c
> index e440b15fbabc..ebd4631b685b 100644
> --- a/drivers/ras/cec.c
> +++ b/drivers/ras/cec.c
> @@ -489,7 +489,7 @@ static int __init create_debugfs_nodes(void)
> }
>
> d = debugfs_create_dir("cec", dfs);
> - if (!d) {
> + if (IS_ERR(d)) {
> pr_warn("Error creating cec debugfs node!\n");
> return -1;
> }
next prev parent reply other threads:[~2024-08-23 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 13:23 [PATCH v2] drivers:block:Use IS_ERR() to check debugfs_create_dir() return value Yang Ruibin
2024-08-23 8:29 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-22 12:41 Yang Ruibin
2024-08-22 12:50 ` Yang Ruibin
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=20240823092959.00000c90@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=11162571@vivo.com \
--cc=apw@canonical.com \
--cc=bp@alien8.de \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mingo@kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=tony.luck@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