From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, armbru@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] typedefs.h cleanup
Date: Thu, 15 Nov 2018 15:17:50 -0600 [thread overview]
Message-ID: <20181115211752.1295571-1-eblake@redhat.com> (raw)
Prompted by my review of xiezhide's work. No semantic change, but
not technically a bug fix, so I don't care if it goes in 3.1 or
waits for 4.0.
Eric Blake (2):
typedefs: (Re-)sort entries alphabetically
numa: Match struct to typedef name
include/qemu/typedefs.h | 12 ++++++------
include/sysemu/numa.h | 2 +-
2 files changed, 7 insertions(+), 7 deletions(-)
--
2.17.2
next reply other threads:[~2018-11-15 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 21:17 Eric Blake [this message]
2018-11-15 21:17 ` [Qemu-devel] [PATCH 1/2] typedefs: (Re-)sort entries alphabetically Eric Blake
2018-12-19 8:23 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2018-11-15 21:17 ` [Qemu-devel] [PATCH 2/2] numa: Match struct to typedef name Eric Blake
2018-11-19 23:20 ` Eduardo Habkost
2018-11-15 21:28 ` [Qemu-devel] [PATCH 0/2] typedefs.h cleanup Philippe Mathieu-Daudé
2018-11-16 10:14 ` Markus Armbruster
2018-12-18 19:59 ` Eric Blake
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=20181115211752.1295571-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).