From: Jonathan Corbet <corbet@lwn.net>
To: Ioana Ciornei <ciorneiioana@gmail.com>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: linux-doc@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>,
Maxim Levitsky <mlevitsk@redhat.com>,
Jing Zhang <jingzhangos@google.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: Re: [PATCH 0/4] docs: small fixes
Date: Sun, 25 Jul 2021 14:35:15 -0600 [thread overview]
Message-ID: <87k0leuo70.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210722100356.635078-1-ciorneiioana@gmail.com>
Ioana Ciornei <ciorneiioana@gmail.com> writes:
> From: Ioana Ciornei <ioana.ciornei@nxp.com>
>
> This patch set is just a bundle of small fixes for problems and build
> warnings that I stumbled upon when trying to add a new section of
> documentation.
>
> Ioana Ciornei (4):
> docs: printk-formats: fix build warning
> docs: kvm: fix build warnings
> docs: kvm: properly format code blocks and lists
> docs: networking: dpaa2: fix chapter title format
>
> Documentation/core-api/printk-formats.rst | 1 +
> .../ethernet/freescale/dpaa2/dpio-driver.rst | 1 +
> Documentation/virt/kvm/api.rst | 32 +++++++++++--------
> 3 files changed, 20 insertions(+), 14 deletions(-)
I've applied the set.
Thanks,
jon
prev parent reply other threads:[~2021-07-25 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 10:03 [PATCH 0/4] docs: small fixes Ioana Ciornei
2021-07-22 10:03 ` [PATCH 1/4] docs: printk-formats: fix build warning Ioana Ciornei
2021-07-23 8:12 ` Petr Mladek
2021-07-23 19:26 ` Stephen Boyd
2021-07-22 10:03 ` [PATCH 2/4] docs: kvm: fix build warnings Ioana Ciornei
2021-07-22 10:03 ` [PATCH 3/4] docs: kvm: properly format code blocks and lists Ioana Ciornei
2021-07-22 15:53 ` Jing Zhang
2021-07-22 10:03 ` [PATCH 4/4] docs: networking: dpaa2: fix chapter title format Ioana Ciornei
2021-07-25 20:35 ` 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=87k0leuo70.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=ciorneiioana@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=jingzhangos@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=swboyd@chromium.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 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).