From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: michael.roth@amd.com, jsnow@redhat.com, eblake@redhat.com
Subject: [PATCH 0/2] qapi: Minor fixes around feature names
Date: Tue, 10 May 2022 08:16:43 +0200 [thread overview]
Message-ID: <20220510061645.3209195-1-armbru@redhat.com> (raw)
Markus Armbruster (2):
qapi/expr: Enforce feature naming rules again
docs/devel/qapi-code-gen: Belatedly document feature naming rules
docs/devel/qapi-code-gen.rst | 9 +++++----
scripts/qapi/expr.py | 2 +-
2 files changed, 6 insertions(+), 5 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-10 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 6:16 Markus Armbruster [this message]
2022-05-10 6:16 ` [PATCH 1/2] qapi/expr: Enforce feature naming rules again Markus Armbruster
2022-05-10 6:16 ` [PATCH 2/2] docs/devel/qapi-code-gen: Belatedly document feature naming rules Markus Armbruster
2022-05-16 5:47 ` [PATCH 0/2] qapi: Minor fixes around feature names Markus Armbruster
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=20220510061645.3209195-1-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=michael.roth@amd.com \
--cc=qemu-devel@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 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).