From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org, Dmitry Fleytman <dmitry@daynix.com>,
Jason Wang <jasowang@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] e1000e: QOM property & configuration cleanups
Date: Wed, 26 Oct 2016 17:21:54 -0200 [thread overview]
Message-ID: <1477509718-6969-1-git-send-email-ehabkost@redhat.com> (raw)
This changes some of the QOM property code in e1000e so it uses
regular property type macros, and the usual QOM property naming
style. This also removes unnecessary configuration validation on
migration/loadvm.
Some of the patches break command-line compatibility, but I am
assuming those properties are not being used in production by
anybody.
Eduardo Habkost (4):
e1000e: Use regular DEFINE_PROP_<type> macros for properties
e1000e: No need to validate configuration on migration
e1000e: Rename "disable_vnet_hdr" property to "vnet"
e1000e: Rename "subsys_ven" property to "subsys-vendor"
hw/net/e1000e.c | 50 ++++++++------------------------------------------
1 file changed, 8 insertions(+), 42 deletions(-)
--
2.7.4
next reply other threads:[~2016-10-26 19:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 19:21 Eduardo Habkost [this message]
2016-10-26 19:21 ` [Qemu-devel] [PATCH 1/4] e1000e: Use regular DEFINE_PROP_<type> macros for properties Eduardo Habkost
2016-10-27 3:12 ` Jason Wang
2016-10-27 6:38 ` Dmitry Fleytman
2016-10-27 11:25 ` Eduardo Habkost
2016-10-27 15:13 ` Igor Mammedov
2016-10-27 16:39 ` Eduardo Habkost
2016-10-26 19:21 ` [Qemu-devel] [PATCH 2/4] e1000e: No need to validate configuration on migration Eduardo Habkost
2016-10-27 6:42 ` Dmitry Fleytman
2016-10-27 11:39 ` Eduardo Habkost
2016-10-27 12:22 ` Dr. David Alan Gilbert
2016-10-27 14:28 ` Eduardo Habkost
2016-10-26 19:21 ` [Qemu-devel] [PATCH 3/4] e1000e: Rename "disable_vnet_hdr" property to "vnet" Eduardo Habkost
2016-10-27 6:47 ` Dmitry Fleytman
2016-10-26 19:21 ` [Qemu-devel] [PATCH 4/4] e1000e: Rename "subsys_ven" property to "subsys-vendor" Eduardo Habkost
2016-10-27 6:45 ` Dmitry Fleytman
2016-10-27 11:30 ` Eduardo Habkost
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=1477509718-6969-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=dmitry@daynix.com \
--cc=jasowang@redhat.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).