From: Simon Glass <sjg@chromium.org>
To: Simon Glass <sjg@chromium.org>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
Pratyush Yadav <p.yadav@ti.com>,
Mike Frysinger <vapier@gentoo.org>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH v4 4/5] sf: doc: Add documentation for the 'sf' command
Date: Wed, 24 Nov 2021 12:47:55 -0500 [thread overview]
Message-ID: <CAPnjgZ3UN7HCv+VxL=ZbZgwatLek+hP5uhjaEJMskVQYmk-5ew@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ0NKmTk9ZSrFZFP=Y1VbgkRwgC3isV5O3j50ONgVS6D2A@mail.gmail.com>
Hi Heinrich,
On Sat, 13 Nov 2021 at 08:32, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>
> Am 13. November 2021 15:21:13 MEZ schrieb Simon Glass <sjg@chromium.org>:
> >Hi Heinrich,
> >
> >On Sat, 13 Nov 2021 at 04:34, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> >>
> >> On 9/19/21 23:49, Simon Glass wrote:
> >> > This command is fairly complicated so documentation is useful.
> >> > Unfortunately I an not sure how the MTD side of things works and cannot
> >> > find information about that.
> >> >
> >> > Signed-off-by: Simon Glass <sjg@chromium.org>
> >> >
> >> > Acked-by: Pratyush Yadav <p.yadav@ti.com>
> >> > ---
> >> >
> >> > Changes in v4:
> >> > - Split out the 'const' change into a separate patch
> >> > - Show the 'sf probe' output in the examples
> >> >
> >> > Changes in v2:
> >> > - Many fixes as suggested by Heinrich
> >> >
> >> > doc/usage/index.rst | 1 +
> >> > doc/usage/sf.rst | 245 ++++++++++++++++++++++++++++++++++++++++++++
> >> > 2 files changed, 246 insertions(+)
> >> > create mode 100644 doc/usage/sf.rst
> >> >
Applied to u-boot-dm, thanks!
Applied to u-boot-dm/next, thanks!
next prev parent reply other threads:[~2021-11-24 17:49 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 [this message]
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 ` [PATCH v4 0/5] sf: Add documentation and an 'sf mmap' command 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='CAPnjgZ3UN7HCv+VxL=ZbZgwatLek+hP5uhjaEJMskVQYmk-5ew@mail.gmail.com' \
--to=sjg@chromium.org \
--cc=jagan@amarulasolutions.com \
--cc=p.yadav@ti.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).