public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Mark Brown <broonie@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Lee Jones <lee.jones@linaro.org>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFT 0/4] mfd: regulator: max14577: Remove support for platform data
Date: Tue, 28 Feb 2017 12:34:37 +0100	[thread overview]
Message-ID: <13060664.SiaA6008Pk@amdc3058> (raw)
In-Reply-To: <20170228094740.kgsanxtum6xj2wdt@sirena.org.uk>


Hi,

On Tuesday, February 28, 2017 09:47:40 AM Mark Brown wrote:
> On Mon, Feb 27, 2017 at 04:52:36PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > On Monday, February 27, 2017 05:32:37 PM Krzysztof Kozlowski wrote:
> 
> > > The driver supports two chipsets: max14577 and max77836. As you noted,
> > > the first one is for Gear 1. The second one is present on Gear2 which
> > > is supported by mainline. Simplifying the driver to support only
> > > max77836 would be a task requiring testing. I think review would be in
> > > such case not enough.
> 
> > I think that this shouldn't be a big problem (if no one
> > else volunteers we can do the testing on Gear2 device).
> 
> OTOH is it really gaining us much to remove the functionality vs the
> effort for testing?  Removing the entire driver is fairly
> straightforward but if it's just some extra device support that's
> sitting there not bothering anyone perhaps it's not really a good use of
> time.

We have to test the device from time to time anyway just
to check that upstream support is still working so it
shouldn't be much extra effort.

Leaving the code as it is for now is also okay for me
(till it starts bothering somebody, i.e. people doing
automatic DT bindings coverage/validity checking).

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics

      reply	other threads:[~2017-02-28 12:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170217200214epcas3p4d72abd10d1ce7dbbbcd626bcf452fa37@epcas3p4.samsung.com>
2017-02-17 20:01 ` [RFT 0/4] mfd: regulator: max14577: Remove support for platform data Krzysztof Kozlowski
2017-02-17 20:01   ` [RFT 1/4] mfd: max14577: Explicitly depend on OF Krzysztof Kozlowski
2017-02-17 20:01   ` [RFT 2/4] mfd: max14577: Export OF module alias information Krzysztof Kozlowski
2017-02-17 20:01   ` [RFT 3/4] regulator: max14577: Remove support for platform data Krzysztof Kozlowski
2017-02-18  0:02     ` Mark Brown
2017-02-17 20:02   ` [RFT 4/4] mfd: max14577: Remove platform data and instantiation from I2C Krzysztof Kozlowski
2017-02-27 12:55   ` [RFT 0/4] mfd: regulator: max14577: Remove support for platform data Bartlomiej Zolnierkiewicz
2017-02-27 15:32     ` Krzysztof Kozlowski
2017-02-27 15:52       ` Bartlomiej Zolnierkiewicz
2017-02-28  9:47         ` Mark Brown
2017-02-28 11:34           ` Bartlomiej Zolnierkiewicz [this message]

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=13060664.SiaA6008Pk@amdc3058 \
    --to=b.zolnierkie@samsung.com \
    --cc=broonie@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=krzk@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --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