From: Jan Kiszka <jan.kiszka@siemens.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Lee Jones <lee.jones@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd: intel_quark_i2c_gpio: Add support for SIMATIC IOT2000 platform
Date: Fri, 19 May 2017 16:35:43 +0200 [thread overview]
Message-ID: <4e6685b1-6676-4fb1-da76-aaf65e0cb7ba@siemens.com> (raw)
In-Reply-To: <CAHp75VefMP6er1U+4kcVy9jBJOEBQpTUmXW7j=A87L72cQZ7Hw@mail.gmail.com>
On 2017-05-19 16:22, Andy Shevchenko wrote:
> On Fri, May 19, 2017 at 10:55 AM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> On 2017-05-12 10:12, Lee Jones wrote:
>>> On Tue, 09 May 2017, Andy Shevchenko wrote:
>>> On Tue, 2017-05-09 at 06:40 +0200, Jan Kiszka wrote:
>>>>> The SIMATIC IOT2000 is derived from the Galileo Gen2 board and shares
>>>>> its I2C frequency.
>
>> Apparently, the patch is not yet in mfd-next, so let me retract it: I
>> just realized we should rather do an exact name/asset-tags match here as
>> well (like for exar and stmmac).
>>
>> Moreover, I'd like to rework the DMI matching along Andy's suggestion
>> and use native matching methods (dmi_system_id table) instead of the
>> current open-code one. Patches will follow soon.
>
> Suggestion was made regarding another driver and code.
>
Yes, but it applies here analogously, just like to stmmac_pci.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2017-05-19 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 4:40 Jan Kiszka
2017-05-09 11:34 ` Andy Shevchenko
2017-05-12 8:12 ` Lee Jones
2017-05-19 7:55 ` Jan Kiszka
2017-05-19 14:22 ` Andy Shevchenko
2017-05-19 14:35 ` Jan Kiszka [this message]
2017-05-22 9:36 ` Lee Jones
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=4e6685b1-6676-4fb1-da76-aaf65e0cb7ba@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
/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®