From: Jie Deng <jie.deng@intel.com> To: Randy Dunlap <rdunlap@infradead.org>, linux-i2c@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org Cc: 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 Subject: Re: [PATCH v2] i2c: virtio: add a virtio i2c frontend driver Date: Mon, 14 Sep 2020 09:16:12 +0800 [thread overview] Message-ID: <39c7c5ba-58c2-2b94-d4a5-59dff1b6f556@intel.com> (raw) In-Reply-To: <f235538d-63d6-2c16-4d9e-d913f15cdcf7@infradead.org> On 2020/9/11 11:53, Randy Dunlap wrote: > On 9/10/20 8:48 PM, Jie Deng wrote: >> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig >> index 293e7a0..70c8e30 100644 >> --- a/drivers/i2c/busses/Kconfig >> +++ b/drivers/i2c/busses/Kconfig >> @@ -21,6 +21,17 @@ config I2C_ALI1535 >> This driver can also be built as a module. If so, the module >> will be called i2c-ali1535. >> >> +config I2C_VIRTIO >> + tristate "Virtio I2C Adapter" >> + depends on VIRTIO >> + help >> + If you say yes to this option, support will be included for the virtio >> + i2c adapter driver. The hardware can be emulated by any device model > I2C > preferably > I will fix this typo. Thank you. >> + software according to the virtio protocol. >> + >> + This driver can also be built as a module. If so, the module >> + will be called i2c-virtio. >> + >> config I2C_ALI1563 >> tristate "ALI 1563" >> depends on PCI > > thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Jie Deng <jie.deng@intel.com> To: Randy Dunlap <rdunlap@infradead.org>, linux-i2c@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org Cc: Sergey.Semin@baikalelectronics.ru, bjorn.andersson@linaro.org, loic.poulain@linaro.org, yu1.wang@intel.com, mst@redhat.com, krzk@kernel.org, tali.perry1@gmail.com, wsa@kernel.org, wsa+renesas@sang-engineering.com, jarkko.nikula@linux.intel.com, rppt@kernel.org, shuo.a.liu@intel.com, andriy.shevchenko@linux.intel.com, conghui.chen@intel.com, jdelvare@suse.de Subject: Re: [PATCH v2] i2c: virtio: add a virtio i2c frontend driver Date: Mon, 14 Sep 2020 09:16:12 +0800 [thread overview] Message-ID: <39c7c5ba-58c2-2b94-d4a5-59dff1b6f556@intel.com> (raw) In-Reply-To: <f235538d-63d6-2c16-4d9e-d913f15cdcf7@infradead.org> On 2020/9/11 11:53, Randy Dunlap wrote: > On 9/10/20 8:48 PM, Jie Deng wrote: >> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig >> index 293e7a0..70c8e30 100644 >> --- a/drivers/i2c/busses/Kconfig >> +++ b/drivers/i2c/busses/Kconfig >> @@ -21,6 +21,17 @@ config I2C_ALI1535 >> This driver can also be built as a module. If so, the module >> will be called i2c-ali1535. >> >> +config I2C_VIRTIO >> + tristate "Virtio I2C Adapter" >> + depends on VIRTIO >> + help >> + If you say yes to this option, support will be included for the virtio >> + i2c adapter driver. The hardware can be emulated by any device model > I2C > preferably > I will fix this typo. Thank you. >> + software according to the virtio protocol. >> + >> + This driver can also be built as a module. If so, the module >> + will be called i2c-virtio. >> + >> config I2C_ALI1563 >> tristate "ALI 1563" >> depends on PCI > > thanks. _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2020-09-14 1:16 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-11 3:48 [PATCH v2] i2c: virtio: add a virtio i2c frontend driver Jie Deng 2020-09-11 3:48 ` Jie Deng 2020-09-11 3:53 ` Randy Dunlap 2020-09-11 3:53 ` Randy Dunlap 2020-09-14 1:16 ` Jie Deng [this message] 2020-09-14 1:16 ` Jie Deng 2020-09-14 2:46 ` Jason Wang 2020-09-14 2:46 ` Jason Wang 2020-09-14 3:43 ` Jie Deng 2020-09-14 3:43 ` Jie Deng 2020-09-14 14:48 ` Dan Carpenter 2020-09-14 14:48 ` Dan Carpenter 2020-09-14 14:48 ` Dan Carpenter 2020-09-14 14:48 ` Dan Carpenter 2020-09-14 15:24 ` Andy Shevchenko 2020-09-14 15:24 ` Andy Shevchenko 2020-09-14 15:47 ` Dan Carpenter 2020-09-14 15:47 ` Dan Carpenter 2020-09-14 15:47 ` Dan Carpenter 2020-09-14 15:47 ` Dan Carpenter 2020-09-14 16:08 ` Andy Shevchenko 2020-09-14 16:08 ` Andy Shevchenko 2020-09-14 16:08 ` Andy Shevchenko 2020-09-12 21:57 kernel test robot
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=39c7c5ba-58c2-2b94-d4a5-59dff1b6f556@intel.com \ --to=jie.deng@intel.com \ --cc=Sergey.Semin@baikalelectronics.ru \ --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=rdunlap@infradead.org \ --cc=rppt@kernel.org \ --cc=shuo.a.liu@intel.com \ --cc=tali.perry1@gmail.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.