mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sascha Weisenberger <sascha.weisenberger@siemens.com>
Subject: Re: [PATCH v2 1/2] mfd: intel_quark_i2c_gpio: Use dmi_system_id table for retrieving frequency
Date: Mon, 22 May 2017 19:23:01 +0100	[thread overview]
Message-ID: <20170522182301.d2nwqf2qdlzstyye@dell> (raw)
In-Reply-To: <CAHp75VexGvWcsV_qAHN=F06JD6JTAB6MgQWikAqtr6t7099ahw@mail.gmail.com>

On Mon, 22 May 2017, Andy Shevchenko wrote:

> On Mon, May 22, 2017 at 8:38 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> > On 2017-05-22 19:36, Andy Shevchenko wrote:
> >> On Mon, May 22, 2017 at 8:34 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> >>> On 2017-05-22 19:26, Andy Shevchenko wrote:
> >>>> On Mon, May 22, 2017 at 8:25 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> >>>>> On 2017-05-22 19:20, Andy Shevchenko wrote:
> >>>>>> On Mon, May 22, 2017 at 8:18 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> >>>>>>> On 2017-05-22 19:12, Andy Shevchenko wrote:
> >>>>>>>> On Mon, May 22, 2017 at 1:53 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
> 
> >>>>>> And since there is no difference to the frequency the name is enough.
> >>>>>> So, I wouldn't go with this series as is. See above.
> >>>>>
> >>>>> Nope: Just like for the stmmac, we need to include the asset tags to
> >>>>> avoid matching variations of the devices which may carry the same board
> >>>>> name. While I will try to avoid that this happens, we are better safe
> >>>>> than sorry here.
> >>>>
> >>>> Do we have an issue right now?
> >>>> Yes / No
> >>>
> >>> Andy, we are trying to design a robust upstream driver here, no ad-hoc
> >>> BSP that will not survive the hardware anyway.
> >>
> >> You didn't answer my question...
> >>
> >> I do not see a good point to solve the issue that might happen in the future.
> >>
> >
> > While I do - that's why your question is misleading.
> >
> > Then let's leave the decision up to the maintainer.
> 
> Lee, just for your convenience I'm repeating myself here:
> 
> I do not like this series at all since it tries to solve non-existing
> issue in over-engineering way.
> 
> If you on opposite side I will be happy to help reviewing it.

New code looks cleaner and appears to use an already defined API.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2017-05-22 18:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 10:53 [PATCH v2 0/2] mfd: intel_quark_i2c_gpio: Refactor and support for IOT2000 Jan Kiszka
2017-05-22 10:53 ` [PATCH v2 1/2] mfd: intel_quark_i2c_gpio: Use dmi_system_id table for retrieving frequency Jan Kiszka
2017-05-22 17:12   ` Andy Shevchenko
2017-05-22 17:18     ` Jan Kiszka
2017-05-22 17:20       ` Andy Shevchenko
2017-05-22 17:25         ` Jan Kiszka
2017-05-22 17:26           ` Andy Shevchenko
2017-05-22 17:34             ` Jan Kiszka
2017-05-22 17:36               ` Andy Shevchenko
2017-05-22 17:38                 ` Jan Kiszka
2017-05-22 17:42                   ` Andy Shevchenko
2017-05-22 18:23                     ` Lee Jones [this message]
2017-05-22 18:37                       ` Andy Shevchenko
2017-05-22 18:47                         ` Jan Kiszka
2017-05-22 19:35                           ` Andy Shevchenko
2017-05-22 10:53 ` [PATCH v2 2/2] mfd: intel_quark_i2c_gpio: Add support for SIMATIC IOT2000 platform Jan Kiszka
2017-05-23 15:02 ` [PATCH v2 0/2] mfd: intel_quark_i2c_gpio: Refactor and support for IOT2000 Andy Shevchenko
2017-05-30  8:13 ` 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=20170522182301.d2nwqf2qdlzstyye@dell \
    --to=lee.jones@linaro.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sascha.weisenberger@siemens.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

all inboxes | Powered by JetHome®