From: Eduardo Habkost <ehabkost@redhat.com>
To: Dmitry Fleytman <dmitry@daynix.com>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 4/4] e1000e: Rename "subsys_ven" property to "subsys-vendor"
Date: Thu, 27 Oct 2016 09:30:43 -0200 [thread overview]
Message-ID: <20161027113043.GF5057@thinpad.lan.raisama.net> (raw)
In-Reply-To: <5225E3C1-219A-482B-B556-2CBBADCFE766@daynix.com>
On Thu, Oct 27, 2016 at 09:45:27AM +0300, Dmitry Fleytman wrote:
[...]
> > @@ -524,7 +524,6 @@ static int e1000e_post_load(void *opaque, int version_id)
> > E1000EState *s = opaque;
> >
> > trace_e1000e_cb_post_load();
> > -
>
> This hunk should not be in this patch.
Sorry, this is a leftover from conflict resolution when I was
reordering the patches. This can be removed when committing, or I
can send a new version. Jason?
--
Eduardo
prev parent reply other threads:[~2016-10-27 11:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 19:21 [Qemu-devel] [PATCH 0/4] e1000e: QOM property & configuration cleanups Eduardo Habkost
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 [this message]
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=20161027113043.GF5057@thinpad.lan.raisama.net \
--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).