qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio: avoid leading underscores for helpers
Date: Tue, 10 Mar 2015 17:34:27 +0100	[thread overview]
Message-ID: <20150310173153-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150310170347.48bf09ca.cornelia.huck@de.ibm.com>

On Tue, Mar 10, 2015 at 05:03:47PM +0100, Cornelia Huck wrote:
> On Tue, 10 Mar 2015 15:27:24 +0100
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > On Tue, Mar 10, 2015 at 03:22:29PM +0100, Cornelia Huck wrote:
> > > On Tue, 10 Mar 2015 15:12:14 +0100
> > > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > > 
> > > > On Tue, Mar 10, 2015 at 02:32:15PM +0100, Cornelia Huck wrote:
> > > > > Commit ef546f1275f6563e8934dd5e338d29d9f9909ca6 ("virtio: add
> > > > > feature checking helpers") introduced a helper __virtio_has_feature.
> > > > > We don't want to use reserved identifiers, though, so let's
> > > > > rename __virtio_has_feature to virtio_has_feature and virtio_has_feature
> > > > > to virtio_vdev_has_feature.
> > > > 
> > > > I don't think it's urgent to fix in master.
> > > > Let's focus on getting virtio 1.0 branch merged instead.
> > > 
> > > I stumbled over this actually when trying to update my virtio-1 branch.
> > > I already did that change there (as promised in
> > > <20141212110701.0c6d879b.cornelia.huck@de.ibm.com>), but it got lost
> > > somewhere in my moving chaos.
> > > 
> > > What's the status of your virtio-1.0 branch?
> > 
> > virtio pci works there too now, so I started looking at upstreaming
> > stuff from that branch.  Already did some.
> > 
> > > Would it be worthwile for
> > > me to rebase on top of it so I can figure out which changes I have not
> > > yet sent out?
> > 
> > Absolutely.
> 
> OK, it's actually not that much:
> 
> - this change :)
> - All ccw accesses are BE (see
>   <20150121133922.1b3e7ceb.cornelia.huck@de.ibm.com>). I'll do two
>   patches: One for the existing ccws which will go via my tree and one
>   for the new set-revision ccw which should be squashed into that patch.

Will rebasing virtio-1.0 on top of master after your patch
is upstream do the trick as well?

> - Use legacy/non-legacy feature bit getters instead of
>   revision-specific ones (see
>   <20150130151049.2e4c5331.cornelia.huck@de.ibm.com>). Should probably
>   replace the existing patches introducing get_features_rev and using it
>   in virtio-blk.

Right, but for that, let's get it all in working order using patches on
top, first.  Then, re-split logically.

> Also, it seems there are some r-bs that had been given for my patches
> that are missing on your branch.

I might have missed some - can you hunt up the msg ids?

  reply	other threads:[~2015-03-10 16:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 13:32 [Qemu-devel] [PATCH] virtio: avoid leading underscores for helpers Cornelia Huck
2015-03-10 14:12 ` Michael S. Tsirkin
2015-03-10 14:22   ` Cornelia Huck
2015-03-10 14:27     ` Michael S. Tsirkin
2015-03-10 16:03       ` Cornelia Huck
2015-03-10 16:34         ` Michael S. Tsirkin [this message]
2015-03-10 17:05           ` Cornelia Huck
2015-03-10 17:22             ` [Qemu-devel] [PATCH] virtio: legacy features callback Cornelia Huck
2015-03-11  9:57             ` [Qemu-devel] [PATCH 0/2] virtio-ccw: be accesses Cornelia Huck
2015-03-11  9:57             ` [Qemu-devel] [PATCH 1/2] virtio-ccw: assure BE accesses Cornelia Huck
2015-03-13  9:44               ` Cornelia Huck
2015-03-11  9:57             ` [Qemu-devel] [PATCH 2/2] virtio-ccw: assure be accesses for set-revision Cornelia Huck
2015-03-11 12:39               ` Thomas Huth

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=20150310173153-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=cornelia.huck@de.ibm.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).