From: Sascha Hauer <sha@pengutronix.de>
To: Wolfram Sang <wsa@kernel.org>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] commands: nand: add missing parameters to help
Date: Tue, 21 Mar 2023 09:13:01 +0100 [thread overview]
Message-ID: <20230321081301.GG7446@pengutronix.de> (raw)
In-Reply-To: <20230319153931.23867-1-wsa@kernel.org>
On Sun, Mar 19, 2023 at 04:39:31PM +0100, Wolfram Sang wrote:
> Signed-off-by: Wolfram Sang <wsa@kernel.org>
> ---
> commands/Kconfig | 4 +++-
> commands/nand.c | 2 +-
> 2 files changed, 4 insertions(+), 2 deletions(-)
Applied, thanks
Sascha
>
> diff --git a/commands/Kconfig b/commands/Kconfig
> index 27769950d9..76dfca2dfd 100644
> --- a/commands/Kconfig
> +++ b/commands/Kconfig
> @@ -1950,12 +1950,14 @@ config CMD_NAND
> help
> NAND flash handling
>
> - Usage: nand [-adb] NANDDEV
> + Usage: nand [-adbgi] NANDDEV
>
> Options:
> -a register a bad block aware device ontop of a normal NAND device
> -d deregister a bad block aware device
> -b OFFS mark block at OFFSet as bad
> + -g OFFS mark block at OFFSet as good
> + -i info. Show information about bad blocks
>
> config CMD_NANDTEST
> tristate
> diff --git a/commands/nand.c b/commands/nand.c
> index 67e43eba30..d07444aee0 100644
> --- a/commands/nand.c
> +++ b/commands/nand.c
> @@ -165,7 +165,7 @@ BAREBOX_CMD_HELP_END
> BAREBOX_CMD_START(nand)
> .cmd = do_nand,
> BAREBOX_CMD_DESC("NAND flash handling")
> - BAREBOX_CMD_OPTS("[-adb] NANDDEV")
> + BAREBOX_CMD_OPTS("[-adbgi] NANDDEV")
> BAREBOX_CMD_GROUP(CMD_GRP_HWMANIP)
> BAREBOX_CMD_HELP(cmd_nand_help)
> BAREBOX_CMD_END
> --
> 2.35.1
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-03-21 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 15:39 [PATCH] commands: nand: add missing parameters to help Wolfram Sang
2023-03-21 8:13 ` Sascha Hauer [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=20230321081301.GG7446@pengutronix.de \
--to=sha@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=wsa@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.