From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Laxman Dewangan <ldewangan@nvidia.com>,
javier@osg.samsung.com, mturquette@baylibre.com,
robh+dt@kernel.org, linux@armlinux.org.uk
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Javier Martinez Canillas <javier@dowhile0.org>
Subject: Re: [PATCH V2 4/4] clk: max77686: Add support for MAX77620 clocks
Date: Fri, 17 Jun 2016 08:12:28 +0200 [thread overview]
Message-ID: <576394CC.7010101@samsung.com> (raw)
In-Reply-To: <5763905F.4020504@nvidia.com>
On 06/17/2016 07:53 AM, Laxman Dewangan wrote:
>
> On Friday 17 June 2016 11:33 AM, Krzysztof Kozlowski wrote:
>> On 06/16/2016 03:23 PM, Laxman Dewangan wrote:
>>> config COMMON_CLK_MAX77686
>>> - tristate "Clock driver for Maxim 77686/77802 MFD"
>>> - depends on MFD_MAX77686
>>> + tristate "Clock driver for Maxim 77686/77802/MAX77620 MFD"
>> You missed Javier's comment here. Just
>> "Maxim 77686/77802/77620"
>
> Sigh.. did not see this comment when going one by one.. really missed..
> I will collect all Reviewed/ack/tested and will post V3 with fixing this.
No problem.
I think the device names could be in numerical order, so:
Maxim 77620/77686/77802
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 4/4] clk: max77686: Add support for MAX77620 clocks
Date: Fri, 17 Jun 2016 08:12:28 +0200 [thread overview]
Message-ID: <576394CC.7010101@samsung.com> (raw)
In-Reply-To: <5763905F.4020504@nvidia.com>
On 06/17/2016 07:53 AM, Laxman Dewangan wrote:
>
> On Friday 17 June 2016 11:33 AM, Krzysztof Kozlowski wrote:
>> On 06/16/2016 03:23 PM, Laxman Dewangan wrote:
>>> config COMMON_CLK_MAX77686
>>> - tristate "Clock driver for Maxim 77686/77802 MFD"
>>> - depends on MFD_MAX77686
>>> + tristate "Clock driver for Maxim 77686/77802/MAX77620 MFD"
>> You missed Javier's comment here. Just
>> "Maxim 77686/77802/77620"
>
> Sigh.. did not see this comment when going one by one.. really missed..
> I will collect all Reviewed/ack/tested and will post V3 with fixing this.
No problem.
I think the device names could be in numerical order, so:
Maxim 77620/77686/77802
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-06-17 6:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 13:23 [PATCH V2 0/4] clk: Combine MAX77686 and MAX77802 driver and extend for MAX77620 Laxman Dewangan
2016-06-16 13:23 ` Laxman Dewangan
2016-06-16 13:23 ` Laxman Dewangan
2016-06-16 13:23 ` [PATCH V2 1/4] clk: max77686: Combine Maxim max77686 and max77802 driver Laxman Dewangan
2016-06-16 13:23 ` Laxman Dewangan
2016-06-16 13:23 ` Laxman Dewangan
2016-06-17 6:01 ` Krzysztof Kozlowski
2016-06-17 6:01 ` Krzysztof Kozlowski
2016-06-16 13:23 ` [PATCH V2 2/4] clk: Combine DT binding doc for max77686 and max77802 Laxman Dewangan
2016-06-16 13:23 ` Laxman Dewangan
2016-06-16 13:23 ` Laxman Dewangan
2016-06-16 13:57 ` Javier Martinez Canillas
2016-06-16 13:57 ` Javier Martinez Canillas
2016-06-17 5:58 ` Krzysztof Kozlowski
2016-06-17 5:58 ` Krzysztof Kozlowski
2016-06-16 13:23 ` [PATCH V2 3/4] clk: max77686: Add DT binding details for PMIC MAX77620 Laxman Dewangan
2016-06-16 13:23 ` Laxman Dewangan
2016-06-16 13:23 ` Laxman Dewangan
2016-06-16 14:02 ` Javier Martinez Canillas
2016-06-16 14:02 ` Javier Martinez Canillas
2016-06-16 14:02 ` Javier Martinez Canillas
2016-06-17 5:59 ` Krzysztof Kozlowski
2016-06-17 5:59 ` Krzysztof Kozlowski
2016-06-16 13:23 ` [PATCH V2 4/4] clk: max77686: Add support for MAX77620 clocks Laxman Dewangan
2016-06-16 13:23 ` Laxman Dewangan
2016-06-16 13:23 ` Laxman Dewangan
2016-06-16 14:07 ` Javier Martinez Canillas
2016-06-16 14:07 ` Javier Martinez Canillas
2016-06-17 6:03 ` Krzysztof Kozlowski
2016-06-17 6:03 ` Krzysztof Kozlowski
2016-06-17 5:53 ` Laxman Dewangan
2016-06-17 5:53 ` Laxman Dewangan
2016-06-17 5:53 ` Laxman Dewangan
2016-06-17 6:12 ` Krzysztof Kozlowski [this message]
2016-06-17 6:12 ` Krzysztof Kozlowski
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=576394CC.7010101@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=javier@dowhile0.org \
--cc=javier@osg.samsung.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=robh+dt@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 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.