From: Jie Deng <jie.deng@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@redhat.com>, Wolfram Sang <wsa@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: "Vincent Guittot" <vincent.guittot@linaro.org>,
"Jason Wang" <jasowang@redhat.com>,
"Bill Mills" <bill.mills@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
virtio-dev@lists.oasis-open.org, stratos-dev@op-lists.linaro.org,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Arnd Bergmann" <arnd@kernel.org>
Subject: Re: [PATCH V5 0/2] virtio: i2c: Allow zero-length transactions
Date: Wed, 13 Oct 2021 10:25:53 +0800 [thread overview]
Message-ID: <50491e03-dc86-e765-f761-b397bdf79fba@intel.com> (raw)
In-Reply-To: <cover.1634037711.git.viresh.kumar@linaro.org>
On 2021/10/12 19:23, Viresh Kumar wrote:
> Hi,
>
> Arnd suggested (over IRC) to split this into two patches for better readability
> and so here is a resend. The eventual specification hasn't changed at all.
>
> V4->V5:
> - Split into two patches.
>
> V3->V4:
> - Add a new mandatory feature flag.
>
> V2->V3:
> - Add conformance clauses that require that the flag is consistent with the
> buffer.
>
> V1->V2:
> - Name the buffer-less request as zero-length request.
>
> ------
>
> I did try to follow the discussion you guys had during V4, where we added
> support for multiple buffers for the same request, which I think is unnecessary
> now, after introduction of the VIRTIO_I2C_FLAGS_FAIL_NEXT flag.
>
> https://lists.oasis-open.org/archives/virtio-comment/202011/msg00005.html
>
> And so starting this discussion again, because we need to support stuff
> like: i2cdetect -q <i2c-bus-number>, which issues a zero-length SMBus
> Quick command.
>
> Viresh Kumar (2):
> virtio: i2c: No need to have separate read-write buffers
> virtio: i2c: Allow zero-length transactions
LGTM. Thanks Viresh.
Reviewed-by: Jie Deng <jie.deng@intel.com>
prev parent reply other threads:[~2021-10-13 2:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 11:23 [PATCH V5 0/2] virtio: i2c: Allow zero-length transactions Viresh Kumar
2021-10-12 11:23 ` [PATCH V5 1/2] virtio: i2c: No need to have separate read-write buffers Viresh Kumar
2021-10-12 13:58 ` Arnd Bergmann
2021-10-12 11:23 ` [PATCH V5 2/2] virtio: i2c: Allow zero-length transactions Viresh Kumar
2021-10-12 14:09 ` Arnd Bergmann
2021-10-13 2:32 ` [virtio-dev] " Jie Deng
2021-10-13 3:39 ` Viresh Kumar
2021-10-13 4:07 ` [virtio-dev] " Jie Deng
2021-10-13 4:12 ` Viresh Kumar
2021-10-13 9:26 ` [virtio-dev] " Cornelia Huck
2021-10-13 9:33 ` Viresh Kumar
2021-10-13 9:44 ` [virtio-dev] " Cornelia Huck
2021-10-13 10:43 ` Viresh Kumar
2021-10-13 11:10 ` [virtio-dev] " Cornelia Huck
2021-10-13 2:25 ` Jie Deng [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=50491e03-dc86-e765-f761-b397bdf79fba@intel.com \
--to=jie.deng@intel.com \
--cc=alex.bennee@linaro.org \
--cc=arnd@kernel.org \
--cc=bill.mills@linaro.org \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stratos-dev@op-lists.linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=wsa@kernel.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