From: Tom Rini <trini@konsulko.com>
To: Angus Ainslie <angus@akkea.ca>
Cc: "NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
u-boot@lists.denx.de, Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Teresa Remmet <t.remmet@phytec.de>,
Adam Ford <aford173@gmail.com>,
Tim Harvey <tharvey@gateworks.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Ilko Iliev <iliev@ronetix.at>,
kernel@puri.sm
Subject: Re: [PATCH 13/13] doc: librem5: add Librem5 documentation
Date: Mon, 17 Jan 2022 11:59:47 -0500 [thread overview]
Message-ID: <20220117165947.GN2631111@bill-the-cat> (raw)
In-Reply-To: <20220117150735.218886-14-angus@akkea.ca>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On Mon, Jan 17, 2022 at 07:07:35AM -0800, Angus Ainslie wrote:
> Initial commit of the Librem5 documentation
>
> Signed-off-by: Angus Ainslie <angus@akkea.ca>
> ---
> doc/board/purism/librem5/librem5.rst | 60 ++++++++++++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 doc/board/purism/librem5/librem5.rst
If you don't also update the index files, this won't be included, or
will give an error? Also, I suspect there's some problems about
headings and so forth, please make sure "make htmldocs" is happy.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-01-17 17:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 15:07 [PATCH 00/13] Add support for the Purism Librem5 Phone Angus Ainslie
2022-01-17 15:07 ` [PATCH 01/13] MAINTAINERS: add Purism to the maintainers file Angus Ainslie
2022-01-17 16:59 ` Tom Rini
2022-01-17 15:07 ` [PATCH 02/13] arm: dts: add the Purism devicetree files Angus Ainslie
2022-01-17 16:59 ` Tom Rini
2022-01-17 17:51 ` Angus Ainslie
2022-01-17 18:25 ` Tom Rini
2022-01-17 18:52 ` Angus Ainslie
2022-01-17 19:42 ` Tom Rini
2022-01-17 15:07 ` [PATCH 03/13] arm: imx8m: add Purism Librem5 Kconfig Angus Ainslie
2022-01-17 15:07 ` [PATCH 04/13] configs: add the Librem5 defconfig Angus Ainslie
2022-01-17 15:07 ` [PATCH 05/13] include: configs: add the librem5.h include file Angus Ainslie
2022-01-17 16:59 ` Tom Rini
2022-01-17 15:07 ` [PATCH 06/13] board: librem5: add the u-boot source for the Librem5 Angus Ainslie
2022-01-17 15:07 ` [PATCH 07/13] board: librem5: add the u-boot header " Angus Ainslie
2022-01-17 15:07 ` [PATCH 08/13] board: librem5: add the SPL source " Angus Ainslie
2022-01-17 15:07 ` [PATCH 09/13] board: librem5: add the LPDDR4 " Angus Ainslie
2022-01-17 15:07 ` [PATCH 11/13] board: librem5: add Librem5 MAINTAINERS file Angus Ainslie
2022-01-17 15:07 ` [PATCH 12/13] board: librem5: add Librem5 build files Angus Ainslie
2022-01-17 15:07 ` [PATCH 13/13] doc: librem5: add Librem5 documentation Angus Ainslie
2022-01-17 16:59 ` Tom Rini [this message]
2022-01-17 16:59 ` [PATCH 00/13] Add support for the Purism Librem5 Phone Tom Rini
2022-01-17 17:14 ` Angus Ainslie
2022-01-17 17:15 ` Angus Ainslie
2022-01-17 17:50 ` Tom Rini
2022-01-17 17:49 ` 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=20220117165947.GN2631111@bill-the-cat \
--to=trini@konsulko.com \
--cc=aford173@gmail.com \
--cc=angus@akkea.ca \
--cc=festevam@gmail.com \
--cc=iliev@ronetix.at \
--cc=jagan@amarulasolutions.com \
--cc=kernel@puri.sm \
--cc=marcel.ziswiler@toradex.com \
--cc=peng.fan@nxp.com \
--cc=sbabic@denx.de \
--cc=t.remmet@phytec.de \
--cc=tharvey@gateworks.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
/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