Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: denglingli@chinamobile.com, virtio-dev@lists.oasis-open.org,
	Halil Pasic <pasic@linux.vnet.ibm.com>,
	Ola.Liljedahl@arm.com, brian.a.keating@intel.com,
	Jani.Kokkonen@huawei.com, xin.zeng@intel.com,
	wangxinxin.wang@huawei.com, liang.j.ma@intel.com,
	qemu-devel@nongnu.org, john.griffin@intel.com, agraf@suse.de,
	arei.gonglei@huawei.com, stefanha@redhat.com,
	jianjay.zhou@huawei.com, cornelia.huck@de.ibm.com,
	Varun.Sethi@freescale.com,
	"Longpeng (Mike)" <longpeng2@huawei.com>,
	vincent.jardin@6wind.com, jasowang@redhat.com,
	weidong.huang@huawei.com
Subject: [virtio-dev] Re: [Qemu-devel] [virtio-dev] Re: [v23 1/2] virtio-crypto: Add virtio crypto device specification
Date: Wed, 1 Aug 2018 22:21:26 +0200	[thread overview]
Message-ID: <47e5bc06-6b4d-aab6-db77-c91313d36d87@linux.ibm.com> (raw)
In-Reply-To: <20180727144726-mutt-send-email-mst@kernel.org>



On 07/27/2018 01:51 PM, Michael S. Tsirkin wrote:
> On Thu, Jul 26, 2018 at 06:55:44PM +0200, Halil Pasic wrote:
>> Sorry I did not have any time for this last days. And this
>> to make it worse this is a follow up to something that was
>> half a year ago. That means I have to re-familiarize myself
>> with the topic.
>>
>> If I don't get around to answer in couple of weeks, feel
>> free to ping me.
>>
>> Since from what I've seen most of the questions were of type
>> 'Can we do it like this?', maybe sending out a new version
>> is the best. So people (like me) can read through the whole
>> thing and point out problems if any.
>>
>> Regards,
>> Halil
> 
> 
> While two weeks for review is borderline reasonable as an exception, it
> does trouble me that  we are at v23, for something that is used
> in the field so it's not like we can just change things at will.
> So I hope everyone concerned makes an effort to try to converge on a spec
> ASAP.
> 

What I tried to say: I'm busy with other stuff, and I'm not too
happy to resume a complex topic after 6 months hiatus.

The series is now at v24 and has apparently no acks or r-bs. I don't think
I'm the only one to blame for that.

It seems, I won't have the time to do a conscientious review in a
timely fashion. If the rest of the bunch thinks what we have is good
enough, I am happy to abstain when voting on this -- and avoiding
holding it up any further.

Regards,
Halil


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2018-08-01 20:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1514626559-162312-1-git-send-email-longpeng2@huawei.com>
2017-12-30  9:35 ` [virtio-dev] [v23 2/2] virtio-crypto: Add conformance clauses Longpeng(Mike)
     [not found] ` <1514626559-162312-2-git-send-email-longpeng2@huawei.com>
2018-01-09 17:05   ` [virtio-dev] Re: [Qemu-devel] [v23 1/2] virtio-crypto: Add virtio crypto device specification Halil Pasic
2018-01-09 17:41     ` Michael S. Tsirkin
2018-01-10  5:53     ` Longpeng (Mike)
2018-06-20  3:34       ` Michael S. Tsirkin
2018-03-16 16:27     ` Michael S. Tsirkin
2018-03-16 18:18       ` Halil Pasic
2018-03-19  0:13         ` Michael S. Tsirkin
2018-07-20 12:01     ` Longpeng (Mike)
2018-07-26 16:55       ` Halil Pasic
2018-07-27  0:59         ` Longpeng (Mike)
2018-07-27 11:51         ` Michael S. Tsirkin
2018-08-01 20:21           ` Halil Pasic [this message]
2018-08-02  1:56             ` [virtio-dev] Re: [Qemu-devel] [virtio-dev] " Longpeng (Mike)

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=47e5bc06-6b4d-aab6-db77-c91313d36d87@linux.ibm.com \
    --to=pasic@linux.ibm.com \
    --cc=Jani.Kokkonen@huawei.com \
    --cc=Ola.Liljedahl@arm.com \
    --cc=Varun.Sethi@freescale.com \
    --cc=agraf@suse.de \
    --cc=arei.gonglei@huawei.com \
    --cc=brian.a.keating@intel.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=denglingli@chinamobile.com \
    --cc=jasowang@redhat.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=john.griffin@intel.com \
    --cc=liang.j.ma@intel.com \
    --cc=longpeng2@huawei.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vincent.jardin@6wind.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=wangxinxin.wang@huawei.com \
    --cc=weidong.huang@huawei.com \
    --cc=xin.zeng@intel.com \
    /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