From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jie Deng <jie.deng@intel.com>,
linux-i2c@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, wsa@kernel.org,
wsa+renesas@sang-engineering.com, arnd@arndb.de,
jasowang@redhat.com, andriy.shevchenko@linux.intel.com,
yu1.wang@intel.com, shuo.a.liu@intel.com, conghui.chen@intel.com,
stefanha@redhat.com, gregkh@linuxfoundation.org
Subject: Re: [PATCH v14] i2c: virtio: add a virtio i2c frontend driver
Date: Mon, 6 Sep 2021 10:13:07 +0530 [thread overview]
Message-ID: <20210906044307.se4dcld2wlblieyv@vireshk-i7> (raw)
In-Reply-To: <20210904160059-mutt-send-email-mst@kernel.org>
On 04-09-21, 16:01, Michael S. Tsirkin wrote:
> Same as with qemu bits, I am confused as to what is the status
> of proposed spec changes and whether the driver will work
> with them.
This is already merged as well.
The current version simply fails to transmit the messages in case the
length of a buffer is 0. I have patch ready to make it work with the
proposed spec changes, just waiting for them to be accepted.
> Let's let the dust settle on them then, then
> resubmit?
It doesn't break anything for now since we don't have much users and
we know zero length transfers don't work. I will submit the necessary
changes once spec is finalized.
--
viresh
next prev parent reply other threads:[~2021-09-06 4:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 2:25 Jie Deng
2021-07-09 3:44 ` Viresh Kumar
2021-07-13 15:34 ` Michael S. Tsirkin
2021-07-13 15:38 ` Michael S. Tsirkin
2021-07-14 2:10 ` Viresh Kumar
2021-07-14 8:33 ` Jie Deng
2021-07-22 5:14 ` Viresh Kumar
2021-07-22 6:06 ` Greg KH
2021-07-22 6:11 ` Viresh Kumar
2021-07-22 15:35 ` Wolfram Sang
2021-07-23 2:21 ` Jie Deng
2021-07-23 2:25 ` Viresh Kumar
2021-09-04 20:01 ` Michael S. Tsirkin
2021-09-06 4:43 ` Viresh Kumar [this message]
2021-09-06 6:40 ` Wolfram Sang
2021-09-08 2:07 ` Jie Deng
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=20210906044307.se4dcld2wlblieyv@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=conghui.chen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=jie.deng@intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=shuo.a.liu@intel.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@kernel.org \
--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
all inboxes | Powered by JetHome®