u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	 Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH v4 0/5] sf: Add documentation and an 'sf mmap' command
Date: Fri, 12 Nov 2021 20:17:13 -0700	[thread overview]
Message-ID: <CAPnjgZ3CpqVmQDr9bZcz-4RTYb-jst6xy5Etbfm1R+x6sDf4xg@mail.gmail.com> (raw)
In-Reply-To: <20210919214937.3829422-1-sjg@chromium.org>

Hi Jagan,

On Sun, 19 Sept 2021 at 15:49, Simon Glass <sjg@chromium.org> wrote:
>
> 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 v4:
> - Split out the 'const' change into a separate patch
> - Show the 'sf probe' output in the examples
>
> 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 (5):
>   command: Use a constant pointer for the help
>   sf: Use const for the stage name
>   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    | 308 ++++++++++++++++++++++++++++++++++++++++++++
>  include/command.h   |   2 +-
>  6 files changed, 369 insertions(+), 19 deletions(-)
>  create mode 100644 doc/usage/sf.rst

Any word on this series please?

Regards,
Simon

      parent reply	other threads:[~2021-11-13  3:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19 21:49 [PATCH v4 0/5] sf: Add documentation and an 'sf mmap' command Simon Glass
2021-09-19 21:49 ` [PATCH v4 1/5] command: Use a constant pointer for the help Simon Glass
2021-10-08 12:40   ` Jagan Teki
2021-11-13 11:13   ` Heinrich Schuchardt
2021-11-24 17:47   ` Simon Glass
2021-11-24 17:47   ` Simon Glass
2021-09-19 21:49 ` [PATCH v4 2/5] sf: Use const for the stage name Simon Glass
2021-10-08 12:41   ` Jagan Teki
2021-11-13 11:15   ` Heinrich Schuchardt
2021-11-24 17:47   ` Simon Glass
2021-11-24 17:47   ` Simon Glass
2021-09-19 21:49 ` [PATCH v4 3/5] sf: Tidy up code to avoid #ifdef Simon Glass
2021-09-20 11:08   ` Pratyush Yadav
2021-09-24  2:48     ` Simon Glass
2021-10-08 12:41   ` Jagan Teki
2021-11-24 17:47   ` Simon Glass
2021-11-24 17:47   ` Simon Glass
2021-09-19 21:49 ` [PATCH v4 4/5] sf: doc: Add documentation for the 'sf' command Simon Glass
2021-10-08 12:42   ` Jagan Teki
2021-11-13 11:34   ` Heinrich Schuchardt
2021-11-13 14:21     ` Simon Glass
2021-11-13 15:26       ` Heinrich Schuchardt
2021-11-13 18:14         ` Simon Glass
2021-11-24 17:47         ` Simon Glass
2021-11-24 17:47         ` Simon Glass
2021-09-19 21:49 ` [PATCH v4 5/5] sf: Provide a command to access memory-mapped SPI Simon Glass
2021-10-08 12:47   ` Jagan Teki
2021-10-08 20:29     ` Simon Glass
2021-11-13 11:47   ` Heinrich Schuchardt
2021-11-25  0:12     ` Simon Glass
2021-11-13  3:17 ` Simon Glass [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=CAPnjgZ3CpqVmQDr9bZcz-4RTYb-jst6xy5Etbfm1R+x6sDf4xg@mail.gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).