[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <541138D0.6090808@lategoodbye.de>
Date: Thu, 11 Sep 2014 07:53:20 +0200
From: Stefan Wahren <info@...egoodbye.de>
To: Fabio Estevam <festevam@...il.com>
CC: Mark Brown <broonie@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"shawn.guo@...aro.org" <shawn.guo@...aro.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
Pawel Moll <Pawel.Moll@....com>,
"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
"galak@...eaurora.org" <galak@...eaurora.org>,
"stefan.wahren@...e.com" <stefan.wahren@...e.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH RFC 2/3] ARM: regulator: add Freescale MXS regulator driver
Hi Fabio,
Am 10.09.2014 20:54, schrieb Fabio Estevam:
> Hi Stefan,
>
> On Wed, Sep 10, 2014 at 2:32 PM, Stefan Wahren <info@...egoodbye.de> wrote:
>> Hi Mark,
>>
>> Am 10.09.2014 17:13, schrieb Mark Brown:
>>>
>>> On Wed, Sep 10, 2014 at 03:18:53PM +0100, Mark Rutland wrote:
>>>>
>>>> On Tue, Sep 09, 2014 at 08:17:17PM +0100, Stefan Wahren wrote:
>>>
>>>
>>> Ugh, this looks like it might be a regulator driver but since the
>>> subject line was "ARM: " I deleted it unread - if your changelog looks
>>> different to all the other changelogs in the subsystem it probably needs
>>> changing.
>>
>>
>> sorry about the confusion, i will remove ARM in the next version.
>>
>> Changelog? I didn't send a changelog because it was my first version.
>>
>> Should i resend this version only to you?
>
> In the cover letter of this RFC series you mentioned that this has not
> been tested on real hardware.
>
> What about sending a new version of this series (with the RFC prefix
> removed and with Mark Rutland's suggestion implemented) tested on a
> mx28 board and also with the Subject of the regulator patch changed to
> 'regulator: add support for mxs regulator" with Mark Brown on Cc?
>
that's the same idea i had about the first real version of my patch.
Unfortunately i can do the porting only in my spare time. So i try to
avoid with the RFC series the situation, that i spend many days in
development and testing, but after it the regulator guys says it went in
the complete wrong direction. The advice about the anatop regulator was
helpful, but there is still some unsureness.
I will try to get a Duckbill, so i can do testing at home.
Thanks
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists