linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Lee Jones <lee.jones@linaro.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH v5 0/9] mfd: max14577: Add support for MAX77836
Date: Wed, 16 Apr 2014 20:36:50 +0900	[thread overview]
Message-ID: <534E6B52.9080706@samsung.com> (raw)
In-Reply-To: <1397646165.6147.16.camel@AMDC1943>

On 04/16/2014 08:02 PM, Krzysztof Kozlowski wrote:
> On śro, 2014-04-16 at 19:51 +0900, Chanwoo Choi wrote:
>> Hi Krzysztof,
>>
>> On 04/16/2014 07:44 PM, Krzysztof Kozlowski wrote:
>>> On śro, 2014-04-16 at 11:28 +0100, Lee Jones wrote:
>>>>> This is first part of fifth version of patchset adding support for
>>>>> MAX77836 device to the max14577 driver.
>>>>>
>>>>> I decided to split the patchset into smaller parts. I hope this would
>>>>> help in getting necessary review/acks from maintainers.
>>>>>
>>>>> The first part introduces changes in max14577 driver and adds support
>>>>> for MAX77836 in MFD, extcon and regulator drivers. Most of these
>>>>> patches already have required acks from maintainers.
>>>>> Full v4 patchset can be found here:
>>>>> http://thread.gmane.org/gmane.linux.kernel/1654267
>>>>
>>>> So what's the plan for this driver now? What's missing? Do you have
>>>> all the Acks you need? If so, I'm happy to apply this patch-set and
>>>> supply a pull-request to the other maintainers.
>>>
>>> Next patches (part 2):
>>> 1. charger: max14577: Add support for MAX77836 charger
>>> 2. power: max17040: Add ID for MAX77836 Fuel Gauge block
>>> 3. regulator/mfd: max14577: Export symbols for calculating charger 
>>>    current
>>> 4. charger: max14577: Configure battery-dependent settings from DTS
>>> 5. Documentation: mfd: max14577: Add device tree bindings document
>>> 6. regulator: max14577: Implement SUSPEND mode for MAX77836 LDO-s
>>>
>>> They are quite independent from each other so I think it would be the
>>> best if you could prepare an immutable branch with first part of
>>> patches.
>>
>> I have to modify all extcon device drivers for some reason,
>> If your patchset including extcon patch apply other git repository,
>> this patchset may have potential merge conflict.
>>
>> If you possible, following patchset would divide two patchset for each mfd/extcon
>> to remove potential merge conflict in 3.15 merge window.
>> - [PATCH v5 0/9] mfd: max14577: Add support for MAX77836
> 
> I think we can resolve this after preparing by Lee the immutable branch
> with this patches. You could pull it so your changes to extcon-max14577
> would be on newest version.

I'm reluctant for your suggestion.
IMO, If Lee agree, I'd like to apply this patchset on extcon git
after getting ack for all patchset from maintainer.
And you would send your patchset (part 2) after 3.15 merge window.

Thanks,
Chanwoo Choi


  reply	other threads:[~2014-04-16 11:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14  9:17 [PATCH v5 0/9] mfd: max14577: Add support for MAX77836 Krzysztof Kozlowski
2014-04-14  9:17 ` [PATCH v5 1/9] extcon: max14577: Change extcon name instead of static name according to device type Krzysztof Kozlowski
2014-04-14  9:17 ` [PATCH v5 2/9] mfd: max14577: Add muic prefix to regmap config Krzysztof Kozlowski
2014-04-15  6:36   ` Chanwoo Choi
2014-04-16 10:22   ` Lee Jones
2014-04-14  9:17 ` [PATCH v5 3/9] mfd: max14577: Add detection of device type Krzysztof Kozlowski
2014-04-14  9:17 ` [PATCH v5 4/9] extcon: max14577: Add max14577 prefix to muic_irqs Krzysztof Kozlowski
2014-04-14  9:17 ` [PATCH v5 5/9] extcon: max14577: Choose muic_irqs according to device type Krzysztof Kozlowski
2014-04-14  9:17 ` [PATCH v5 6/9] mfd: max14577: Add MAX14577 prefix to IRQ defines Krzysztof Kozlowski
2014-04-15  6:37   ` Chanwoo Choi
2014-04-16 10:27   ` Lee Jones
2014-04-14  9:17 ` [PATCH v5 7/9] mfd: max77836: Add MAX77836 support to max14577 driver Krzysztof Kozlowski
2014-04-14  9:17 ` [PATCH v5 8/9] extcon: max14577: Add support for MAX77836 Krzysztof Kozlowski
2014-04-14  9:17 ` [PATCH v5 9/9] regulator: max14577: Add support for MAX77836 regulators Krzysztof Kozlowski
2014-04-15  6:50 ` [PATCH v5 0/9] mfd: max14577: Add support for MAX77836 Chanwoo Choi
2014-04-16 10:28 ` Lee Jones
2014-04-16 10:44   ` Krzysztof Kozlowski
2014-04-16 10:51     ` Chanwoo Choi
2014-04-16 11:02       ` Krzysztof Kozlowski
2014-04-16 11:36         ` Chanwoo Choi [this message]
2014-04-16 12:17           ` Lee Jones
2014-04-16 14:21             ` Chanwoo Choi
2014-04-16 11:08     ` Lee Jones
2014-04-16 11:13       ` Krzysztof Kozlowski
2014-04-16 12:18         ` Lee Jones
2014-04-23 11:52           ` Krzysztof Kozlowski
2014-04-23 13:04             ` 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=534E6B52.9080706@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=broonie@kernel.org \
    --cc=k.kozlowski@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=sameo@linux.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: 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;
as well as URLs for NNTP newsgroup(s).