All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: "Longpeng (Mike)" <longpeng2@huawei.com>,
	Halil Pasic <pasic@linux.vnet.ibm.com>,
	virtio-dev@lists.oasis-open.org, Ola.Liljedahl@arm.com,
	brian.a.keating@intel.com, wangxinxin.wang@huawei.com,
	liang.j.ma@intel.com, jasowang@redhat.com, xin.zeng@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, Jani.Kokkonen@huawei.com,
	vincent.jardin@6wind.com, denglingli@chinamobile.com,
	weidong.huang@huawei.com
Subject: Re: [Qemu-devel] [virtio-dev] Re: [v23 1/2] virtio-crypto: Add virtio crypto device specification
Date: Fri, 27 Jul 2018 14:51:18 +0300	[thread overview]
Message-ID: <20180727144726-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <a332a516-16dc-1e50-3ea6-b68571880cb7@linux.ibm.com>

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.

> On 07/20/2018 02:01 PM, Longpeng (Mike) wrote:
> > 
> > 
> > On 2018/1/10 1:05, Halil Pasic wrote:
> > 
> > > 
> > > 
> > > On 12/30/2017 10:35 AM, Longpeng(Mike) wrote:
> > > > From: Gonglei <arei.gonglei@huawei.com>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org

WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: "Longpeng (Mike)" <longpeng2@huawei.com>,
	Halil Pasic <pasic@linux.vnet.ibm.com>,
	virtio-dev@lists.oasis-open.org, Ola.Liljedahl@arm.com,
	brian.a.keating@intel.com, wangxinxin.wang@huawei.com,
	liang.j.ma@intel.com, jasowang@redhat.com, xin.zeng@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, Jani.Kokkonen@huawei.com,
	vincent.jardin@6wind.com, denglingli@chinamobile.com,
	weidong.huang@huawei.com
Subject: Re: [virtio-dev] Re: [Qemu-devel] [v23 1/2] virtio-crypto: Add virtio crypto device specification
Date: Fri, 27 Jul 2018 14:51:18 +0300	[thread overview]
Message-ID: <20180727144726-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <a332a516-16dc-1e50-3ea6-b68571880cb7@linux.ibm.com>

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.

> On 07/20/2018 02:01 PM, Longpeng (Mike) wrote:
> > 
> > 
> > On 2018/1/10 1:05, Halil Pasic wrote:
> > 
> > > 
> > > 
> > > On 12/30/2017 10:35 AM, Longpeng(Mike) wrote:
> > > > From: Gonglei <arei.gonglei@huawei.com>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org

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


  parent reply	other threads:[~2018-07-27 11:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-30  9:35 [Qemu-devel] [v23 0/2] virtio-crypto: virtio crypto device specification Longpeng(Mike)
2017-12-30  9:35 ` [Qemu-devel] [v23 1/2] virtio-crypto: Add " Longpeng(Mike)
2018-01-09 17:05   ` Halil Pasic
2018-01-09 17:05     ` [virtio-dev] " Halil Pasic
2018-01-09 17:41     ` Michael S. Tsirkin
2018-01-09 17:41       ` [virtio-dev] " Michael S. Tsirkin
2018-01-10  5:53     ` Longpeng (Mike)
2018-01-10  5:53       ` [virtio-dev] " Longpeng (Mike)
2018-06-20  3:34       ` [Qemu-devel] [virtio-dev] " Michael S. Tsirkin
2018-06-20  3:34         ` [virtio-dev] Re: [Qemu-devel] " Michael S. Tsirkin
2018-06-20  6:15         ` [Qemu-devel] [virtio-dev] " Longpeng (Mike)
2018-03-16 16:27     ` Michael S. Tsirkin
2018-03-16 16:27       ` [virtio-dev] Re: [Qemu-devel] " Michael S. Tsirkin
2018-03-16 18:18       ` [Qemu-devel] [virtio-dev] " Halil Pasic
2018-03-16 18:18         ` [virtio-dev] Re: [Qemu-devel] " Halil Pasic
2018-03-19  0:13         ` [Qemu-devel] [virtio-dev] " Michael S. Tsirkin
2018-03-19  0:13           ` [virtio-dev] Re: [Qemu-devel] " Michael S. Tsirkin
2018-07-20 12:01     ` Longpeng (Mike)
2018-07-20 12:01       ` [virtio-dev] " Longpeng (Mike)
2018-07-26 16:55       ` Halil Pasic
2018-07-26 16:55         ` [virtio-dev] " Halil Pasic
2018-07-27  0:59         ` Longpeng (Mike)
2018-07-27  0:59           ` [virtio-dev] " Longpeng (Mike)
2018-07-27 11:51         ` Michael S. Tsirkin [this message]
2018-07-27 11:51           ` Michael S. Tsirkin
2018-08-01 20:21           ` [Qemu-devel] [virtio-dev] " Halil Pasic
2018-08-01 20:21             ` [virtio-dev] " Halil Pasic
2018-08-02  1:56             ` Longpeng (Mike)
2018-08-02  1:56               ` [virtio-dev] " Longpeng (Mike)
2017-12-30  9:35 ` [Qemu-devel] [v23 2/2] virtio-crypto: Add conformance clauses Longpeng(Mike)
2017-12-30  9:35   ` [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=20180727144726-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.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=pasic@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.