From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Christian Heusel <christian@heusel.eu>,
David Woodhouse <dwmw2@infradead.org>,
Richard Weinberger <richard@nod.at>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Cc: <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] jffs2: print symbolic error name instead of error code
Date: Sun, 18 Feb 2024 09:13:27 +0800 [thread overview]
Message-ID: <e4d00360-bb36-cfe1-5c0c-8e5b1c7bebc0@huawei.com> (raw)
In-Reply-To: <20240211003907.167891-1-christian@heusel.eu>
在 2024/2/11 8:39, Christian Heusel 写道:
> Utilize the %pe print specifier to get the symbolic error name as a
> string (i.e "-ENOMEM") in the log message instead of the error code to
> increase its readablility.
>
> This change was suggested in
> https://lore.kernel.org/all/92972476-0b1f-4d0a-9951-af3fc8bc6e65@suswa.mountain/
>
> Signed-off-by: Christian Heusel <christian@heusel.eu>
> ---
> fs/jffs2/background.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
>
> diff --git a/fs/jffs2/background.c b/fs/jffs2/background.c
> index 6da92ecaf66d..bb0ee1a59e71 100644
> --- a/fs/jffs2/background.c
> +++ b/fs/jffs2/background.c
> @@ -44,8 +44,8 @@ int jffs2_start_garbage_collect_thread(struct jffs2_sb_info *c)
>
> tsk = kthread_run(jffs2_garbage_collect_thread, c, "jffs2_gcd_mtd%d", c->mtd->index);
> if (IS_ERR(tsk)) {
> - pr_warn("fork failed for JFFS2 garbage collect thread: %ld\n",
> - -PTR_ERR(tsk));
> + pr_warn("fork failed for JFFS2 garbage collect thread: %pe\n",
> + tsk);
> complete(&c->gc_thread_exit);
> ret = PTR_ERR(tsk);
> } else {
> --
> 2.43.1
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> .
>
next prev parent reply other threads:[~2024-02-18 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 0:39 Christian Heusel
2024-02-18 1:13 ` Zhihao Cheng [this message]
2024-03-11 12:47 ` Christian Heusel
2024-03-11 12:56 ` Richard Weinberger
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=e4d00360-bb36-cfe1-5c0c-8e5b1c7bebc0@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=christian@heusel.eu \
--cc=dwmw2@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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®