From: Wolfram Sang <wsa@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Arnd Bergmann" <arnd@arndb.de>, "Jie Deng" <jie.deng@intel.com>,
"Linux I2C" <linux-i2c@vger.kernel.org>,
"open list:DRM DRIVER FOR QEMU'S CIRRUS DEVICE"
<virtualization@lists.linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
yu1.wang@intel.com, conghui.chen@intel.com,
"Stefan Hajnoczi" <stefanha@redhat.com>,
gregkh <gregkh@linuxfoundation.org>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
jiedeng@alumni.sjtu.edu.cn
Subject: Re: [PATCH v15] i2c: virtio: add a virtio i2c frontend driver
Date: Wed, 28 Jul 2021 11:33:12 +0200 [thread overview]
Message-ID: <YQEkWL3ZQzbiMVl6@kunai> (raw)
In-Reply-To: <20210726035902.b6zo72r6mdlxyf7w@vireshk-i7>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
> > This will now conflict with Viresh's patch that adds all the other IDs.
> > Not sure if there is anything to be done about that.
>
> An easier way of avoiding all such conflicts can be:
>
> - Michael applies my first patch (which sync's the device id's from specs) for
> 5.14-rc4. Rest of the patches can go for 5.15.
>
> - And then Wolfram applies this series over rc4 instead of rc1.
>
> Or we can leave the conflict there for Linus to handle.
Or Michael creates an immutable branch for me to pull in. I am fine with
either approach. A bit in favor of the immutable branch.
Other than that, I am happy with the virtio driver itself and ready to
apply it once we decide how to handle the dependency.
Thank you everyone for the hard work and the patience!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-07-28 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 5:44 [PATCH v15] i2c: virtio: add a virtio i2c frontend driver Jie Deng
2021-07-23 9:03 ` Arnd Bergmann
2021-07-26 3:59 ` Viresh Kumar
2021-07-28 9:33 ` Wolfram Sang [this message]
2021-07-27 2:15 ` Jie Deng
2021-07-27 4:23 ` Viresh Kumar
2021-08-17 20:22 ` Wolfram Sang
2021-08-18 1:29 ` 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=YQEkWL3ZQzbiMVl6@kunai \
--to=wsa@kernel.org \
--cc=alex.bennee@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=jiedeng@alumni.sjtu.edu.cn \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=stefanha@redhat.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=virtualization@lists.linux-foundation.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).