From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Isaku Yamahata <isaku.yamahata@intel.com>,
Xiaoyao Li <xiaoyao.li@intel.com>,
Yu Zhang <yu.c.zhang@linux.intel.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH v2 0/3] Documentation fixes for kvm-upstream-workaround
Date: Wed, 17 Aug 2022 19:48:34 +0700 [thread overview]
Message-ID: <20220817124837.422695-1-bagasdotme@gmail.com> (raw)
Here is documentation fixes for kvm-upstream-workaround branch of TDX
tree [1]. The fixes below should be self-explanatory.
Changes since v1 [2]:
- Wrap description of "shutdown" status to fit the table
- Add Reported-by from kernel test robot
[1]: https://github.com/intel/tdx.git
[2]: https://lore.kernel.org/linux-doc/20220817095405.199662-1-bagasdotme@gmail.com/
Bagas Sanjaya (3):
Documentation: ABI: tdx: fix formatting in ABI documentation
Documentation: ABI: tdx: grammar improv
Documentation: kvm: enclose the final closing brace in code block
Documentation/ABI/testing/sysfs-firmware-tdx | 62 ++++++++++----------
Documentation/virt/kvm/api.rst | 2 +-
2 files changed, 33 insertions(+), 31 deletions(-)
base-commit: 85c097fdd1667a842a9e75d8f658fc16bd72981a
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2022-08-17 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 12:48 Bagas Sanjaya [this message]
2022-08-17 12:48 ` [PATCH v2 1/3] Documentation: ABI: tdx: fix formatting in ABI documentation Bagas Sanjaya
2022-08-17 12:48 ` [PATCH v2 2/3] Documentation: ABI: tdx: grammar improv Bagas Sanjaya
2022-08-17 12:48 ` [PATCH v2 3/3] Documentation: kvm: enclose the final closing brace in code block Bagas Sanjaya
2022-08-23 5:57 ` [PATCH v2 0/3] Documentation fixes for kvm-upstream-workaround Isaku Yamahata
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=20220817124837.422695-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=chao.p.peng@linux.intel.com \
--cc=corbet@lwn.net \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=xiaoyao.li@intel.com \
--cc=yu.c.zhang@linux.intel.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