From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Jagan Teki <jagan@amarulasolutions.com>,
Simon Glass <sjg@chromium.org>,
Mike Frysinger <vapier@gentoo.org>
Subject: [PATCH v3 0/4] sf: Add documentation and an 'sf mmap' command
Date: Sun, 1 Aug 2021 15:12:41 -0600 [thread overview]
Message-ID: <20210801211245.2208037-1-sjg@chromium.org> (raw)
This little series adds documentation and a few other tidy-ups to the
'sf' command.
It also provides a way to access memory-mapped SPI via the command line.
Changes in v3:
- Add configuration and return value also
Changes in v2:
- Explain why 'usage' cannot be const
- Many fixes as suggested by Heinrich
Simon Glass (4):
command: Use a constant pointer for the help
sf: Tidy up code to avoid #ifdef
sf: doc: Add documentation for the 'sf' command
sf: Provide a command to access memory-mapped SPI
arch/Kconfig | 2 +
cmd/Kconfig | 8 ++
cmd/sf.c | 67 +++++++---
doc/usage/index.rst | 1 +
doc/usage/sf.rst | 304 ++++++++++++++++++++++++++++++++++++++++++++
include/command.h | 2 +-
6 files changed, 365 insertions(+), 19 deletions(-)
create mode 100644 doc/usage/sf.rst
--
2.32.0.554.ge1b32706d8-goog
next reply other threads:[~2021-08-01 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 21:12 Simon Glass [this message]
2021-08-01 21:12 ` [PATCH v3 1/4] command: Use a constant pointer for the help Simon Glass
2021-08-01 21:12 ` [PATCH v3 2/4] sf: Tidy up code to avoid #ifdef Simon Glass
2021-08-02 16:28 ` Pratyush Yadav
2021-08-01 21:12 ` [PATCH v3 3/4] sf: doc: Add documentation for the 'sf' command Simon Glass
2021-08-02 16:38 ` Pratyush Yadav
2021-08-01 21:12 ` [PATCH v3 4/4] sf: Provide a command to access memory-mapped SPI Simon Glass
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=20210801211245.2208037-1-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=jagan@amarulasolutions.com \
--cc=u-boot@lists.denx.de \
--cc=vapier@gentoo.org \
--cc=xypron.glpk@gmx.de \
/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.