From: lagarcia@linux.ibm.com
To: qemu-ppc@nongnu.org
Cc: Leonardo Garcia <lagarcia@br.ibm.com>,
danielhb413@gmail.com, qemu-devel@nongnu.org, clg@kaod.org
Subject: [PATCH 0/3] rSTify ppc-spapr-hotplug.txt
Date: Wed, 12 Jan 2022 10:52:13 -0300 [thread overview]
Message-ID: <cover.1641995057.git.lagarcia@br.ibm.com> (raw)
From: Leonardo Garcia <lagarcia@br.ibm.com>
This patch series depend on previously sent patch "docs: Clarification
and formatting changes in ppc docs." which is already included in latest
pull request from Cédric.
It is important to notice that I focused mainly in the layout of the
document, and not so much on the content. My understanding is that some
sections, such as Hot plug/unplug events and Hot plug/unplug event
structure may need updates based on what I saw in the code, but I don't
have the expertise today to rewrite these sections. Hopefully someone
will be able to update them.
Leonardo Garcia (3):
docs: rSTify ppc-spapr-hotplug.txt.
docs: Rename ppc-spapr-hotplug.txt to ppc-spapr-hotplug.rst.
Link new ppc-spapr-hotplug.rst file to pseries.rst.
docs/specs/ppc-spapr-hotplug.rst | 510 +++++++++++++++++++++++++++++++
docs/specs/ppc-spapr-hotplug.txt | 409 -------------------------
docs/system/ppc/pseries.rst | 2 +-
3 files changed, 511 insertions(+), 410 deletions(-)
create mode 100644 docs/specs/ppc-spapr-hotplug.rst
delete mode 100644 docs/specs/ppc-spapr-hotplug.txt
--
2.34.1
next reply other threads:[~2022-01-12 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 13:52 lagarcia [this message]
2022-01-12 13:52 ` [PATCH 1/3] docs: rSTify ppc-spapr-hotplug.txt lagarcia
2022-01-13 20:32 ` Daniel Henrique Barboza
2022-01-12 13:52 ` [PATCH 2/3] docs: Rename ppc-spapr-hotplug.txt to ppc-spapr-hotplug.rst lagarcia
2022-01-13 20:32 ` Daniel Henrique Barboza
2022-01-12 13:52 ` [PATCH 3/3] Link new ppc-spapr-hotplug.rst file to pseries.rst lagarcia
2022-01-13 20:34 ` Daniel Henrique Barboza
2022-01-18 12:03 ` [PATCH 0/3] rSTify ppc-spapr-hotplug.txt Cédric Le Goater
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=cover.1641995057.git.lagarcia@br.ibm.com \
--to=lagarcia@linux.ibm.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=lagarcia@br.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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.