From: Jie Deng <jie.deng@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-i2c@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, mst@redhat.com,
jasowang@redhat.com, wsa+renesas@sang-engineering.com,
wsa@kernel.org, andriy.shevchenko@linux.intel.com,
jarkko.nikula@linux.intel.com, jdelvare@suse.de,
Sergey.Semin@baikalelectronics.ru, krzk@kernel.org,
rppt@kernel.org, loic.poulain@linaro.org, tali.perry1@gmail.com,
bjorn.andersson@linaro.org, shuo.a.liu@intel.com,
conghui.chen@intel.com, yu1.wang@intel.com,
"Alex Bennée" <alex.bennee@linaro.org>,
"Vincent Guittot" <vincent.guittot@linaro.org>
Subject: Re: [PATCH v4] i2c: virtio: add a virtio i2c frontend driver
Date: Fri, 26 Feb 2021 14:36:04 +0800 [thread overview]
Message-ID: <96f88e54-ebc7-bfda-310c-ca75b3e09398@intel.com> (raw)
In-Reply-To: <20210226042126.rix5gjxqrazb6sao@vireshk-i7>
On 2021/2/26 12:21, Viresh Kumar wrote:
> On 26-02-21, 10:46, Jie Deng wrote:
>> This v4 was the old version before the specification was acked by the virtio
>> tc.
>>
>> Following is the latest specification.
>>
>> https://raw.githubusercontent.com/oasis-tcs/virtio-spec/master/virtio-i2c.tex
>>
>> I will send the v5 since the host/guest ABI changes.
> Okay, now it makes some sense :)
>
> I am interested in this stuff, if possible please keep me Cc'd for following
> versions, thanks.
Sure. I will add you to the Cc list.
prev parent reply other threads:[~2021-02-26 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 1:55 [PATCH v4] i2c: virtio: add a virtio i2c frontend driver Jie Deng
2020-10-12 5:45 ` kernel test robot
2020-11-25 9:35 ` Michael S. Tsirkin
2020-11-26 2:00 ` Jie Deng
2021-02-25 7:21 ` Viresh Kumar
2021-02-26 2:46 ` Jie Deng
2021-02-26 4:21 ` Viresh Kumar
2021-02-26 6:36 ` 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=96f88e54-ebc7-bfda-310c-ca75b3e09398@intel.com \
--to=jie.deng@intel.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=alex.bennee@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=conghui.chen@intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jasowang@redhat.com \
--cc=jdelvare@suse.de \
--cc=krzk@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mst@redhat.com \
--cc=rppt@kernel.org \
--cc=shuo.a.liu@intel.com \
--cc=tali.perry1@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).