From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Cc: lvivier@redhat.com, jasowang@redhat.com, qemu-stable@nongnu.org,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V2 0/2] hw/virtio: fix double use of a virtio flag
Date: Tue, 1 Mar 2016 19:00:43 +0200 [thread overview]
Message-ID: <56D5CABB.6050104@gmail.com> (raw)
In-Reply-To: <1455111073-5600-1-git-send-email-marcel@redhat.com>
On 02/10/2016 03:31 PM, Marcel Apfelbaum wrote:
> To the obvious question of "how did that happen?"
> I can say we had an unlucky break.
> Both Jason and me worked on a new different virtio feature in the same
> time, and they were both merged in the same pull request.
> We both saw BIT 3 as the last used
> https://lists.gnu.org/archive/html/qemu-devel/2015-11/msg03041.html
>
> Commits 1811e64c and a6df8adf use the same virtio feature bit 4
> for different features.
>
> Fix it by using different bits.
> While at it, group all the virtio flags into an enum to avoid that
> in the feature.
>
ping
Thanks,
Marcel
>
> v1 -> v2:
> - Addressed Laurent Vivier's comment:
> - forgot to remove a flag
> - Added teset-by to the first patch
>
> Marcel Apfelbaum (2):
> hw/virtio: fix double use of a virtio flag
> hw/virtio: group virtio flags into an enum
>
> hw/virtio/virtio-pci.h | 17 ++++++++++-------
> 1 file changed, 10 insertions(+), 7 deletions(-)
>
prev parent reply other threads:[~2016-03-01 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 13:31 [Qemu-devel] [PATCH V2 0/2] hw/virtio: fix double use of a virtio flag Marcel Apfelbaum
2016-02-10 13:31 ` [Qemu-devel] [PATCH V2 1/2] " Marcel Apfelbaum
2016-02-23 3:42 ` Jason Wang
2016-02-10 13:31 ` [Qemu-devel] [PATCH V2 2/2] hw/virtio: group virtio flags into an enum Marcel Apfelbaum
2016-02-10 13:37 ` Laurent Vivier
2016-02-23 3:42 ` Jason Wang
2016-03-01 17:00 ` Marcel Apfelbaum [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=56D5CABB.6050104@gmail.com \
--to=marcel.apfelbaum@gmail.com \
--cc=jasowang@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).