From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 4/7] doc: update reference to README.imx8image
Date: Fri, 17 Apr 2020 17:08:07 -0400 [thread overview]
Message-ID: <20200417210807.GF4555@bill-the-cat> (raw)
In-Reply-To: <20200228141816.1644-5-patrick.delaunay@st.com>
On Fri, Feb 28, 2020 at 03:18:13PM +0100, Patrick Delaunay wrote:
> Update reference in many files detected by
> scripts/documentation-file-ref-check
>
> README.imx8image => imx/mkimage/imx8image.txt
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200417/d2365b4a/attachment.sig>
next prev parent reply other threads:[~2020-04-17 21:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 14:18 [PATCH 0/7] doc: Fix some errors pointed out by 'make refcheckdocs' Patrick Delaunay
2020-02-28 14:18 ` [PATCH 1/7] README: update reference to *.README Patrick Delaunay
2020-02-28 14:27 ` Heinrich Schuchardt
2020-04-17 21:07 ` Tom Rini
2020-02-28 14:18 ` [PATCH 2/7] Kconfig: update reference to README.x86 Patrick Delaunay
2020-03-02 19:47 ` Simon Glass
2020-04-17 21:07 ` Tom Rini
2020-02-28 14:18 ` [PATCH 3/7] doc: update reference to README.imximage Patrick Delaunay
2020-04-17 21:08 ` Tom Rini
2020-02-28 14:18 ` [PATCH 4/7] doc: update reference to README.imx8image Patrick Delaunay
2020-04-17 21:08 ` Tom Rini [this message]
2020-02-28 14:18 ` [PATCH 5/7] doc: update reference to README.board Patrick Delaunay
2020-04-17 21:08 ` Tom Rini
2020-02-28 14:18 ` [PATCH 6/7] doc: device-tree-bindings: update reference to binding directory Patrick Delaunay
2020-04-17 21:08 ` Tom Rini
2020-02-28 14:18 ` [PATCH 7/7] arm: imx: update reference to README.mxc_hab Patrick Delaunay
2020-04-17 21:08 ` Tom Rini
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=20200417210807.GF4555@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.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