From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Thorsten Blum <thorsten.blum@linux.dev>,
David Woodhouse <dwmw2@infradead.org>,
Richard Weinberger <richard@nod.at>,
Randy Dunlap <rdunlap@infradead.org>,
Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] jffs2: Use str_yes_no() helper function
Date: Mon, 28 Oct 2024 09:13:46 +0800 [thread overview]
Message-ID: <cb01b563-a636-ed47-4cbd-42c5ed806860@huawei.com> (raw)
In-Reply-To: <20241026111903.112647-2-thorsten.blum@linux.dev>
在 2024/10/26 19:19, Thorsten Blum 写道:
> Remove hard-coded strings by using the str_yes_no() helper function.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> fs/jffs2/nodemgmt.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
> diff --git a/fs/jffs2/nodemgmt.c b/fs/jffs2/nodemgmt.c
> index bbab2bdc71b6..69569864630e 100644
> --- a/fs/jffs2/nodemgmt.c
> +++ b/fs/jffs2/nodemgmt.c
> @@ -15,6 +15,7 @@
> #include <linux/mtd/mtd.h>
> #include <linux/compiler.h>
> #include <linux/sched/signal.h>
> +#include <linux/string_choices.h>
> #include "nodelist.h"
> #include "debug.h"
>
> @@ -317,9 +318,9 @@ static int jffs2_find_nextblock(struct jffs2_sb_info *c)
> And there's no space left. At all. */
> pr_crit("Argh. No free space left for GC. nr_erasing_blocks is %d. nr_free_blocks is %d. (erasableempty: %s, erasingempty: %s, erasependingempty: %s)\n",
> c->nr_erasing_blocks, c->nr_free_blocks,
> - list_empty(&c->erasable_list) ? "yes" : "no",
> - list_empty(&c->erasing_list) ? "yes" : "no",
> - list_empty(&c->erase_pending_list) ? "yes" : "no");
> + str_yes_no(list_empty(&c->erasable_list)),
> + str_yes_no(list_empty(&c->erasing_list)),
> + str_yes_no(list_empty(&c->erase_pending_list)));
> return -ENOSPC;
> }
>
> @@ -883,7 +884,7 @@ int jffs2_thread_should_wake(struct jffs2_sb_info *c)
>
> jffs2_dbg(1, "%s(): nr_free_blocks %d, nr_erasing_blocks %d, dirty_size 0x%x, vdirty_blocks %d: %s\n",
> __func__, c->nr_free_blocks, c->nr_erasing_blocks,
> - c->dirty_size, nr_very_dirty, ret ? "yes" : "no");
> + c->dirty_size, nr_very_dirty, str_yes_no(ret));
>
> return ret;
> }
>
prev parent reply other threads:[~2024-10-28 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 11:19 Thorsten Blum
2024-10-28 1:13 ` Zhihao Cheng [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=cb01b563-a636-ed47-4cbd-42c5ed806860@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=quic_jjohnson@quicinc.com \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=thorsten.blum@linux.dev \
/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®