From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Ran Hongyun <ranhongyun1@huawei.com>, <richard@nod.at>,
<miquel.raynal@bootlin.com>, <vigneshr@ti.com>,
<vapier@gentoo.org>, <artem.bityutskiy@linux.intel.com>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<yangerkun@huawei.com>, <yi.zhang@huawei.com>
Subject: Re: [PATCH 1/2] UBI: fix two issues in the ubi.mtd MODULE_PARM_DESC
Date: Thu, 23 Jul 2026 10:40:31 +0800 [thread overview]
Message-ID: <bdf4872f-cd25-252e-25ab-f34366909f33@huawei.com> (raw)
In-Reply-To: <20260723020233.3079997-2-ranhongyun1@huawei.com>
在 2026/7/23 10:02, Ran Hongyun 写道:
> Fix two issues introduced before:
>
> - The parameter format string was missing the enable_fm and
> need_resv_pool tokens introduced in an earlier commit.
>
> - The bad-block reservation note was misplaced after Example 5
> instead of after Example 3. It was misplaced due to an earlier patch.
>
> Fixes: 83ff59a06663 ("UBI: support ubi_num on mtd.ubi command line")
> Signed-off-by: Ran Hongyun <ranhongyun1@huawei.com>
> ---
> drivers/mtd/ubi/build.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
> diff --git a/drivers/mtd/ubi/build.c b/drivers/mtd/ubi/build.c
> index 674ad87809df..8e5f178168cb 100644
> --- a/drivers/mtd/ubi/build.c
> +++ b/drivers/mtd/ubi/build.c
> @@ -1574,7 +1574,7 @@ static int ubi_mtd_param_parse(const char *val, const struct kernel_param *kp)
> }
>
> module_param_call(mtd, ubi_mtd_param_parse, NULL, NULL, 0400);
> -MODULE_PARM_DESC(mtd, "MTD devices to attach. Parameter format: mtd=<name|num|path>[,<vid_hdr_offs>[,max_beb_per1024[,ubi_num]]].\n"
> +MODULE_PARM_DESC(mtd, "MTD devices to attach. Parameter format: mtd=<name|num|path>[,<vid_hdr_offs>[,max_beb_per1024[,ubi_num[,enable_fm[,need_resv_pool]]]]].\n"
> "Multiple \"mtd\" parameters may be specified.\n"
> "MTD devices may be specified by their number, name, or path to the MTD character device node.\n"
> "Optional \"vid_hdr_offs\" parameter specifies UBI VID header position to be used by UBI. (default value if 0)\n"
> @@ -1587,9 +1587,9 @@ MODULE_PARM_DESC(mtd, "MTD devices to attach. Parameter format: mtd=<name|num|pa
> "Example 1: mtd=/dev/mtd0 - attach MTD device /dev/mtd0.\n"
> "Example 2: mtd=content,1984 mtd=4 - attach MTD device with name \"content\" using VID header offset 1984, and MTD device number 4 with default VID header offset.\n"
> "Example 3: mtd=/dev/mtd1,0,25 - attach MTD device /dev/mtd1 using default VID header offset and reserve 25*nand_size_in_blocks/1024 erase blocks for bad block handling.\n"
> + "\t(e.g. if the NAND *chipset* has 4096 PEB, 100 will be reserved for this UBI device).\n"
> "Example 4: mtd=/dev/mtd1,0,0,5 - attach MTD device /dev/mtd1 to UBI 5 and using default values for the other fields.\n"
> - "example 5: mtd=1,0,0,5 mtd=2,0,0,6,1 - attach MTD device /dev/mtd1 to UBI 5 and disable fastmap; attach MTD device /dev/mtd2 to UBI 6 and enable fastmap.(only works when fastmap is enabled and fm_autoconvert=Y).\n"
> - "\t(e.g. if the NAND *chipset* has 4096 PEB, 100 will be reserved for this UBI device).");
> + "example 5: mtd=1,0,0,5 mtd=2,0,0,6,1 - attach MTD device /dev/mtd1 to UBI 5 and disable fastmap; attach MTD device /dev/mtd2 to UBI 6 and enable fastmap.(only works when fastmap is enabled and fm_autoconvert=Y).\n");
> #ifdef CONFIG_MTD_UBI_FASTMAP
> module_param(fm_autoconvert, bool, 0644);
> MODULE_PARM_DESC(fm_autoconvert, "Set this parameter to enable fastmap automatically on images without a fastmap.");
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-07-23 2:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 2:02 [PATCH 0/2] UBI: fix ubi.mtd MODULE_PARM_DESC issues and add per-device wear-leveling threshold Ran Hongyun
2026-07-23 2:02 ` [PATCH 1/2] UBI: fix two issues in the ubi.mtd MODULE_PARM_DESC Ran Hongyun
2026-07-23 2:40 ` Zhihao Cheng [this message]
2026-07-23 2:02 ` [PATCH 2/2] UBI: support per-device wear-leveling threshold Ran Hongyun
2026-07-23 3:01 ` Zhihao Cheng
2026-07-23 6:06 ` Ran Hongyun
2026-07-23 7:19 ` Richard Weinberger
2026-07-23 8:16 ` Ran Hongyun
2026-07-23 8:30 ` 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=bdf4872f-cd25-252e-25ab-f34366909f33@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=ranhongyun1@huawei.com \
--cc=richard@nod.at \
--cc=vapier@gentoo.org \
--cc=vigneshr@ti.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.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