From: Wolfram Sang <wsa@the-dreams.de>
To: "Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@amd.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Elie Morisse <syniurge@gmail.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
"Singh, Sandeep" <Sandeep.Singh@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v16] i2c: Add drivers for the AMD PCIe MP2 I2C controller
Date: Thu, 28 Feb 2019 11:12:37 +0100 [thread overview]
Message-ID: <20190228101237.GA1010@kunai> (raw)
In-Reply-To: <360a227c-68f9-81f8-bcf4-9aeefa837cc0@amd.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
On Thu, Feb 28, 2019 at 09:56:16AM +0000, Shah, Nehal-bakulchandra wrote:
> Hi Elie,
>
> On 2/26/2019 10:20 PM, Wolfram Sang wrote:
> > Hi Elie,
> >
> >> My apologies for the time it took to apply those changes.
> >
> > No worries. I am super happy that you are still around and willing to
> > continue the work!
> >
> >> I will also start working on an alternate (v17?) version with only one
> >> module and replacing the platform driver by an ACPI lookup as
> >> requested by Bjorn Helgaas, unless Nehal clarifies how AMD plans to
> >> expand the platform driver.
> >
> > Sounds really good to me.
>
> Thanks for the patch. For our upcoming sensor hub design we need MP2-PCIE as independent driver.Hence i am requesting to keep the two separate modules.
CCing Bjorn on this one because he expressed in the past that there
might be other possible designs, too. But I don't know PCIE, so I'd like
to have his expertise at the table.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-28 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 16:12 [PATCH v16] i2c: Add drivers for the AMD PCIe MP2 I2C controller Elie Morisse
2019-02-26 16:23 ` Elie Morisse
2019-02-26 16:50 ` Wolfram Sang
2019-02-28 9:56 ` Shah, Nehal-bakulchandra
2019-02-28 10:12 ` Wolfram Sang [this message]
2019-02-27 16:00 ` kbuild 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=20190228101237.GA1010@kunai \
--to=wsa@the-dreams.de \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=Sandeep.Singh@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=bhelgaas@google.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syniurge@gmail.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 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.