All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: "Longpeng (Mike)" <longpeng2@huawei.com>,
	stefanha@redhat.com, qemu-devel@nongnu.org,
	virtio-dev@lists.oasis-open.org, luonengjun@huawei.com,
	cohuck@redhat.com, denglingli@chinamobile.com,
	Jani.Kokkonen@huawei.com, Ola.Liljedahl@arm.com,
	Varun.Sethi@freescale.com, xin.zeng@intel.com,
	brian.a.keating@intel.com, liang.j.ma@intel.com,
	john.griffin@intel.com, weidong.huang@huawei.com,
	mike.caraman@nxp.com, agraf@suse.de, jasowang@redhat.com,
	nmorey@kalray.eu, vincent.jardin@6wind.com,
	arei.gonglei@hotmail.com, wangxinxin.wang@huawei.com
Subject: Re: [virtio-dev] Re: [Qemu-devel] [PATCH v19 0/2] virtio-crypto: virtio crypto device specification
Date: Wed, 6 Sep 2017 16:52:07 +0300	[thread overview]
Message-ID: <20170906164839-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <7f0b8eb2-9e5c-7507-191d-1aab17c6ff0f@linux.vnet.ibm.com>

On Fri, Sep 01, 2017 at 01:45:45PM +0200, Halil Pasic wrote:
> 
> 
> On 09/01/2017 02:47 AM, Longpeng (Mike) wrote:
> > Ping...
> > 
> > Stefan, Halil, do you have any suggestion ?
> > 
> 
> Hi Longpeng,
> 
> I've ran trough your patch, and it reads much better that
> what I recall v18 used to read like. Because it's been a while
> since v18 doing a conscious review on this will take a considerable
> amount of time (my memories of the issues identified back then
> are very sketchy/vague now). It's on my todo list, but it ain't the
> only item there.

I don't think it's a fair reason to delay the merging though.
No comments in a while says time to merge to me.
There's always a public review period during which more comments
can be addressed.

So I think we should start a ballot on this one.
Mike - if you agree please open an issue in TC issue
tracker.  As a reminder here are the guidelines:


--

When you open an issue (can be fixed afterwards as well):

1. Fill in the reporter in the Environment: field.
2. Shortly describe the issue in the description field
   Preferably add a URL to discussion here or
   in the comments.
   If the mail was copied to virtio-comment or virtio-dev, you can use
        mid.gmane.org/<message-id>
   to quickly locate a mail in the archives.
2. Preferably, fill in all affected versions: in
   "Affects Version/s:".
   This might not apply to e.g. improvement requests.

---

When you propose the issue before the TC meeting:

1. Mark issue as Open
2. Fill in a summary of the final proposed change and
   link to full proposal in "Proposal"
   field.
   [any historical abandoned proposals and extra info can go
    into comments field]
---

Then mail me and the TC and I will start a ballot.

Thanks!

> Btw. I like to have a reference implementation at hand when reviewing
> a spec. What is the status of the (reference) implementation (I mean
> the new stuff like stateless/mux)? I think it would be nice to provide
> this info in the cover letter (e.g. next time, should we need another
> iteration).
> 
> 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

---------------------------------------------------------------------
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.vnet.ibm.com>
Cc: "Longpeng (Mike)" <longpeng2@huawei.com>,
	stefanha@redhat.com, qemu-devel@nongnu.org,
	virtio-dev@lists.oasis-open.org, luonengjun@huawei.com,
	cohuck@redhat.com, denglingli@chinamobile.com,
	Jani.Kokkonen@huawei.com, Ola.Liljedahl@arm.com,
	Varun.Sethi@freescale.com, xin.zeng@intel.com,
	brian.a.keating@intel.com, liang.j.ma@intel.com,
	john.griffin@intel.com, weidong.huang@huawei.com,
	mike.caraman@nxp.com, agraf@suse.de, jasowang@redhat.com,
	nmorey@kalray.eu, vincent.jardin@6wind.com,
	arei.gonglei@hotmail.com, wangxinxin.wang@huawei.com
Subject: Re: [Qemu-devel] [virtio-dev] Re: [PATCH v19 0/2] virtio-crypto: virtio crypto device specification
Date: Wed, 6 Sep 2017 16:52:07 +0300	[thread overview]
Message-ID: <20170906164839-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <7f0b8eb2-9e5c-7507-191d-1aab17c6ff0f@linux.vnet.ibm.com>

On Fri, Sep 01, 2017 at 01:45:45PM +0200, Halil Pasic wrote:
> 
> 
> On 09/01/2017 02:47 AM, Longpeng (Mike) wrote:
> > Ping...
> > 
> > Stefan, Halil, do you have any suggestion ?
> > 
> 
> Hi Longpeng,
> 
> I've ran trough your patch, and it reads much better that
> what I recall v18 used to read like. Because it's been a while
> since v18 doing a conscious review on this will take a considerable
> amount of time (my memories of the issues identified back then
> are very sketchy/vague now). It's on my todo list, but it ain't the
> only item there.

I don't think it's a fair reason to delay the merging though.
No comments in a while says time to merge to me.
There's always a public review period during which more comments
can be addressed.

So I think we should start a ballot on this one.
Mike - if you agree please open an issue in TC issue
tracker.  As a reminder here are the guidelines:


--

When you open an issue (can be fixed afterwards as well):

1. Fill in the reporter in the Environment: field.
2. Shortly describe the issue in the description field
   Preferably add a URL to discussion here or
   in the comments.
   If the mail was copied to virtio-comment or virtio-dev, you can use
        mid.gmane.org/<message-id>
   to quickly locate a mail in the archives.
2. Preferably, fill in all affected versions: in
   "Affects Version/s:".
   This might not apply to e.g. improvement requests.

---

When you propose the issue before the TC meeting:

1. Mark issue as Open
2. Fill in a summary of the final proposed change and
   link to full proposal in "Proposal"
   field.
   [any historical abandoned proposals and extra info can go
    into comments field]
---

Then mail me and the TC and I will start a ballot.

Thanks!

> Btw. I like to have a reference implementation at hand when reviewing
> a spec. What is the status of the (reference) implementation (I mean
> the new stuff like stateless/mux)? I think it would be nice to provide
> this info in the cover letter (e.g. next time, should we need another
> iteration).
> 
> 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

  parent reply	other threads:[~2017-09-06 13:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-26  7:53 [PATCH v19 0/2] virtio-crypto: virtio crypto device specification Longpeng(Mike)
2017-08-26  7:53 ` [Qemu-devel] " Longpeng(Mike)
2017-08-26  7:53 ` [PATCH v19 1/2] virtio-crypto: Add " Longpeng(Mike)
2017-08-26  7:53   ` [Qemu-devel] " Longpeng(Mike)
2017-08-26  7:53 ` [PATCH v19 2/2] virtio-crypto: Add conformance clauses Longpeng(Mike)
2017-08-26  7:53   ` [Qemu-devel] " Longpeng(Mike)
2017-09-01  0:47 ` [PATCH v19 0/2] virtio-crypto: virtio crypto device specification Longpeng (Mike)
2017-09-01  0:47   ` [Qemu-devel] " Longpeng (Mike)
2017-09-01 11:45   ` [virtio-dev] " Halil Pasic
2017-09-01 11:45     ` Halil Pasic
2017-09-02  1:52     ` Longpeng (Mike)
2017-09-02  1:52       ` Longpeng (Mike)
2017-09-06 13:52     ` Michael S. Tsirkin [this message]
2017-09-06 13:52       ` [Qemu-devel] [virtio-dev] " Michael S. Tsirkin
2017-09-06 14:12       ` [virtio-dev] Re: [Qemu-devel] " Halil Pasic
2017-09-06 14:12         ` [Qemu-devel] [virtio-dev] " Halil Pasic
2017-09-08  4:17       ` [virtio-dev] Re: [Qemu-devel] " Longpeng (Mike)
2017-09-08  4:17         ` [Qemu-devel] [virtio-dev] " Longpeng (Mike)
2017-09-08  3:49   ` Michael S. Tsirkin
2017-09-08  3:49     ` [Qemu-devel] " Michael S. Tsirkin
2017-09-08  4:22     ` Longpeng (Mike)
2017-09-08  4:22       ` [Qemu-devel] " Longpeng (Mike)
2017-09-08  4:31       ` [virtio-dev] " Michael S. Tsirkin
2017-09-08  4:31         ` [Qemu-devel] " Michael S. Tsirkin
2017-09-08  6:32         ` Longpeng (Mike)
2017-09-08  6:32           ` [Qemu-devel] " 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=20170906164839-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@hotmail.com \
    --cc=brian.a.keating@intel.com \
    --cc=cohuck@redhat.com \
    --cc=denglingli@chinamobile.com \
    --cc=jasowang@redhat.com \
    --cc=john.griffin@intel.com \
    --cc=liang.j.ma@intel.com \
    --cc=longpeng2@huawei.com \
    --cc=luonengjun@huawei.com \
    --cc=mike.caraman@nxp.com \
    --cc=nmorey@kalray.eu \
    --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.