From: Teresa Remmet <t.remmet@phytec.de>
To: barebox@lists.infradead.org
Subject: [PATCH] commands: nand-bitflip: Add documentation for option '-c'
Date: Tue, 18 Dec 2018 13:40:03 +0100 [thread overview]
Message-ID: <1545136803-42645-1-git-send-email-t.remmet@phytec.de> (raw)
Signed-off-by: Teresa Remmet <t.remmet@phytec.de>
---
commands/nand-bitflip.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/commands/nand-bitflip.c b/commands/nand-bitflip.c
index a8a97c153aa0..cfde2f4040e7 100644
--- a/commands/nand-bitflip.c
+++ b/commands/nand-bitflip.c
@@ -107,6 +107,7 @@ BAREBOX_CMD_HELP_START(nand_bitflip)
BAREBOX_CMD_HELP_TEXT("This command creates bitflips on Nand pages.")
BAREBOX_CMD_HELP_TEXT("Options:")
BAREBOX_CMD_HELP_OPT ("-b <block>", "block to work on")
+BAREBOX_CMD_HELP_OPT ("-c\t", "Check only for bitflips")
BAREBOX_CMD_HELP_OPT ("-o <offset>", "offset in Nand")
BAREBOX_CMD_HELP_OPT ("-r\t", "flip random bits")
BAREBOX_CMD_HELP_OPT ("-n <numbitflips>", "Specify maximum number of bitflips to generate")
--
2.7.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2018-12-18 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 12:40 Teresa Remmet [this message]
2018-12-18 14:08 ` Sascha Hauer
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=1545136803-42645-1-git-send-email-t.remmet@phytec.de \
--to=t.remmet@phytec.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox