[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJuYYwTt+1-zU3092GmrK2GHR=5QDGT-diVcm_0pe3=oqhuQdA@mail.gmail.com>
Date: Mon, 26 Nov 2012 19:16:04 +0530
From: Thomas Abraham <thomas.abraham@...aro.org>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: linux-kernel@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
myungjoo.ham@...sung.com, linux-samsung-soc@...r.kernel.org,
kgene.kim@...sung.com, t.figa@...sung.com,
Karol Lewandowski <k.lewandowsk@...sung.com>,
Rajendra Nayak <rnayak@...com>,
Rob Herring <rob.herring@...xeda.com>,
Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH 3/3] regulator: add device tree support for max8997
On 26 November 2012 15:21, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> On Sat, Nov 24, 2012 at 11:46:51PM +0530, Thomas Abraham wrote:
>
>> The max8997 driver is mainlined. I actually meant to say that, this v6
>> version of dt support patch for max8997, is similar in functionality
>> to the v5 version of this patch. I did prepare this patch based on
>> your latest for-next branch.
>
> I find it hard to believe that this was generated against for-next, this
> was where I tried to apply it...
I tried again to apply this patch on 'for-next' branch of your
regulator tree (git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git)
on top of commit 6aa588f43d4a (Merge remote-tracking branches
'regulator/fix/wm831x', 'regulator/topic/as3711',
'regulator/topic/da9055', 'regulator/topic/hotplug',
'regulator/topic/lp8788'.....)
and this patch applied cleanly. Could you please let me know if there
is anything I need to be doing differently for this.
Thanks,
Thomas.
--
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