From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/1] doc: update Kernel documentation build system
Date: Sat, 23 Jan 2021 12:53:52 -0500 [thread overview]
Message-ID: <20210123175352.GX9782@bill-the-cat> (raw)
In-Reply-To: <20210123174623.GR9782@bill-the-cat>
On Sat, Jan 23, 2021 at 12:46:23PM -0500, Tom Rini wrote:
> On Fri, Jan 01, 2021 at 01:21:11AM +0100, Heinrich Schuchardt wrote:
>
> > Update the docomentation build system according to Linux v5.11-rc1.
> >
> > With this patch we can build the HTML documentation using either of
> > Sphinx 2 and Sphinx 3.
> >
> > Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> > Reviewed-by: Simon Glass <sjg@chromium.org>
>
> Applied to u-boot/master, thanks!
I've had to revert this. While I caught and fixed up in a semi-logical
way one duplicate label problem, there's another now that I see, and
probably many more once I rework that one. It's unclear as well how
best to handle these otherwise logical duplicate labels, such as "eMMC"
in doc/board/microchip/mpfs_icicle.rst for example.
--
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/20210123/17fc8e39/attachment.sig>
next prev parent reply other threads:[~2021-01-23 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 0:21 [PATCH 1/1] doc: update Kernel documentation build system Heinrich Schuchardt
2021-01-07 12:35 ` Simon Glass
2021-01-23 17:46 ` Tom Rini
2021-01-23 17:53 ` Tom Rini [this message]
2021-01-24 21:05 ` Heinrich Schuchardt
2021-01-24 23:59 ` Tom Rini
2021-01-25 0:41 ` Heinrich Schuchardt
2021-01-25 0:49 ` Sean Anderson
2021-01-25 1:37 ` Tom Rini
2021-01-25 1:56 ` Simon Glass
2021-01-26 15:28 ` Heinrich Schuchardt
2021-01-26 16:02 ` Tom Rini
2021-02-01 20:38 ` 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=20210123175352.GX9782@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