From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Jie Deng <jie.deng@intel.com>,
virtio-comment@lists.oasis-open.org,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [virtio-comment] [PATCH] content: Reserve device ID 34 for I2C adapter
Date: Thu, 29 Oct 2020 06:38:38 -0400 [thread overview]
Message-ID: <20201029063707-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200909091554.GH12090@stefanha-x1.localdomain>
On Wed, Sep 09, 2020 at 10:15:54AM +0100, Stefan Hajnoczi wrote:
> On Mon, Sep 07, 2020 at 09:51:53AM +0800, Jie Deng wrote:
> > Request the ID 34 for I2C adapter.
> >
> > Signed-off-by: Jie Deng <jie.deng@intel.com>
> > ---
> > content.tex | 2 ++
> > 1 file changed, 2 insertions(+)
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
send Fixes: tag?
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2020-10-29 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 1:51 [virtio-comment] [PATCH] content: Reserve device ID 34 for I2C adapter Jie Deng
2020-09-09 9:15 ` Stefan Hajnoczi
2020-10-29 10:38 ` Michael S. Tsirkin [this message]
2020-10-30 1:48 ` Jie Deng
2020-10-30 7:54 ` Michael S. Tsirkin
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=20201029063707-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=jie.deng@intel.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@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