From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: "Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org,
"Randy Dunlap" <rdunlap@infradead.org>,
"Nícolas F. R. A. Prado" <nfraprado@protonmail.com>,
"Akira Yokosawa" <akiyks@gmail.com>
Subject: Re: [PATCH 0/2] Fix some issues with DOCS_CSS and DOCS_THEME
Date: Thu, 16 Dec 2021 15:55:21 -0700 [thread overview]
Message-ID: <87y24kcg86.fsf@meer.lwn.net> (raw)
In-Reply-To: <cover.1639212812.git.mchehab+huawei@kernel.org>
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> Hi Jon,
>
> Randy pointed a couple of issues with the DOCS_CSS and DOCS_THEME patchset.
> The two patches in this series address them.
>
> Patch 1 fix the usage of "make O=<dir>".
> Patch 2 fix some documentation issues (a typo and whitespace issues).
>
> Randy, thanks for reporting those!
>
> Regards,
> Mauro
>
> Mauro Carvalho Chehab (2):
> docs: Makefile: use the right path for DOCS_CSS
> docs: address some text issues with css/theme support
>
> Documentation/Makefile | 6 +++---
> Documentation/doc-guide/sphinx.rst | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
Set applied, thanks.
jon
prev parent reply other threads:[~2021-12-16 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 8:56 [PATCH 0/2] Fix some issues with DOCS_CSS and DOCS_THEME Mauro Carvalho Chehab
2021-12-11 8:56 ` [PATCH 1/2] docs: Makefile: use the right path for DOCS_CSS Mauro Carvalho Chehab
2021-12-11 17:12 ` Randy Dunlap
2021-12-11 8:57 ` [PATCH 2/2] docs: address some text issues with css/theme support Mauro Carvalho Chehab
2021-12-11 17:12 ` Randy Dunlap
2021-12-16 22:55 ` Jonathan Corbet [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=87y24kcg86.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nfraprado@protonmail.com \
--cc=rdunlap@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.