From: Cornelia Huck <cohuck@redhat.com>
To: Jie Deng <jie.deng@intel.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, mst@redhat.com,
pbonzini@redhat.com, kraxel@redhat.com,
wsa+renesas@sang-engineering.com,
andriy.shevchenko@linux.intel.com, conghui.chen@intel.com,
yu1.wang@intel.com, shuo.a.liu@intel.com
Subject: Re: [virtio-comment] [PATCH v5] virtio-i2c: add the device specification
Date: Thu, 17 Dec 2020 08:56:39 +0100 [thread overview]
Message-ID: <20201217085639.53c281a9.cohuck@redhat.com> (raw)
In-Reply-To: <efe4a6a1-87f1-9712-fc87-6ee17edff6ae@intel.com>
On Thu, 17 Dec 2020 15:29:57 +0800
Jie Deng <jie.deng@intel.com> wrote:
> Thank you. I will fix them.
>
> On 2020/12/17 1:38, Cornelia Huck wrote:
> > On Wed, 25 Nov 2020 13:55:18 +0800
> > Jie Deng <jie.deng@intel.com> wrote:
> >
> > <some mostly editorial comments; sorry about bringing this up now>
> >
> >> +
> >> +A driver MUST place one segment of an I2C transaction into \field{write_buf} if the
> >>
> >> s/if the/if/
> >>
> >> +
> >> +A device MUST place one segment of an I2C transaction into \field{read_buf} if the
> > s/if/if the/
>
> Do you mean "s/if the/if/" here ?
Yes.
>
> >
> > irst failed one to be VIRTIO_I2C_MSG_ERR.
>
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/
prev parent reply other threads:[~2020-12-17 7:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 5:55 [virtio-comment] [PATCH v5] virtio-i2c: add the device specification Jie Deng
2020-11-25 12:52 ` Andy Shevchenko
2020-11-26 2:58 ` [virtio-comment] " Jie Deng
2020-12-08 1:08 ` Jie Deng
2020-12-16 15:52 ` [virtio-comment] " Stefan Hajnoczi
2020-12-17 7:08 ` Jie Deng
2020-12-17 8:00 ` Michael S. Tsirkin
2020-12-17 10:26 ` Stefan Hajnoczi
2020-12-18 2:06 ` Jie Deng
2020-12-19 19:05 ` Michael S. Tsirkin
2020-12-22 6:11 ` Jie Deng
2020-12-22 11:29 ` Cornelia Huck
2020-12-22 22:31 ` Michael S. Tsirkin
2020-12-24 8:15 ` Jie Deng
2020-12-17 10:43 ` Stefan Hajnoczi
2020-12-16 17:38 ` Cornelia Huck
2020-12-16 19:55 ` Michael S. Tsirkin
2020-12-17 8:38 ` Jie Deng
2020-12-17 19:43 ` Michael S. Tsirkin
2020-12-18 1:21 ` Jie Deng
2020-12-17 7:29 ` Jie Deng
2020-12-17 7:56 ` Cornelia Huck [this message]
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=20201217085639.53c281a9.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=conghui.chen@intel.com \
--cc=jie.deng@intel.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=shuo.a.liu@intel.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yu1.wang@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