From: "Michael S. Tsirkin" <mst@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org,
Cornelia Huck <cohuck@redhat.com>,
Pawel Moll <pawel.moll@arm.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [virtio] Re: [virtio-dev] Re: [virtio] Re: [virtio-dev] [PATCH v3 0/6] rework notifications terminology
Date: Thu, 2 Aug 2018 01:30:16 +0300 [thread overview]
Message-ID: <20180802012748-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <38436869-1a5e-9d17-a1fb-a6049f0f8bd5@linux.ibm.com>
On Wed, Aug 01, 2018 at 03:04:54PM +0200, Halil Pasic wrote:
>
>
> On 07/27/2018 01:45 PM, Michael S. Tsirkin wrote:
> > On Fri, Jul 27, 2018 at 01:33:15PM +0200, Halil Pasic wrote:
> > >
> > >
> > > On 07/17/2018 06:47 PM, Halil Pasic wrote:
> > > > > > >
> > > > > > > OK I see there are acks already - do you want to start voting on this?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > Yes, voting would make sense in my opinion.
> > > > > >
> > > > >
> > > > >
> > > > > I've submitted a github issue. Please let me know if further actions are
> > > > > required.
> > > > >
> > > >
> > > > ping
> > >
> > > ping
> >
> > Oh, sorry, I wasn't clear.
> > What you want to do is
> > 1. post the patches including
> > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/16
> > in the commit log part.
> > 2. proposal must link to oasis archive, not mail-archive.
> >
> > Anyway, I fixed the link and started voting now.
> >
>
> Should post a v4 (or a 'REPOST v3') with the r-b's received for
> v3 and the 'Fixes' tags? I mean the ballot, would not link to the
> final thread then. I'm a bit confused regarding now, but I
> think I understood the process.
I think you are right since ballot started no need for v4.
> FYI I'm on and off starting tomorrow till 5th September. I
> am very likely to make any ballots though, but longer response
> times and lower availability are to be expected.
>
> Thanks,
> Halil
What are we going to do about crypto proposals? I think we do want to
finalize a draft for public review by september, and it seems
very unfortunate not to have that device in the draft at all.
--
MST
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
next prev parent reply other threads:[~2018-08-01 22:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 12:21 [virtio] [PATCH v3 0/6] rework notifications terminology Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 1/6] notifications: unify notifications wording in core Halil Pasic
2018-06-25 14:45 ` [virtio] " Cornelia Huck
2018-06-25 15:15 ` [virtio] Re: [virtio-dev] " Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 2/6] notifications: notifications as basic virtio facility Halil Pasic
2018-06-25 14:37 ` [virtio] " Cornelia Huck
2018-06-25 12:21 ` [virtio] [PATCH v3 3/6] ccw: map common notifications terminology to ccw Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 4/6] pci: map common notifications terminology to PCI Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 5/6] mmio: map common notifications terminology to MMIO Halil Pasic
2018-06-25 14:34 ` [virtio] " Cornelia Huck
2018-06-25 12:21 ` [virtio] [PATCH v3 6/6] notifications: update notifications terminology for devices Halil Pasic
2018-07-02 15:51 ` [virtio] Re: [PATCH v3 0/6] rework notifications terminology Stefan Hajnoczi
2018-07-03 0:01 ` [virtio] Re: [virtio-dev] " Michael S. Tsirkin
2018-07-03 7:45 ` Cornelia Huck
2018-07-03 9:00 ` Halil Pasic
2018-07-03 12:07 ` [virtio] Re: [virtio-dev] " Halil Pasic
2018-07-17 16:47 ` Halil Pasic
2018-07-27 11:33 ` Halil Pasic
2018-07-27 11:45 ` Michael S. Tsirkin
2018-08-01 13:04 ` Halil Pasic
2018-08-01 22:30 ` Michael S. Tsirkin [this message]
2018-08-02 17:12 ` Halil Pasic
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=20180802012748-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pawel.moll@arm.com \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.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