[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFRkauDJbEZCn-qdnv_WzQSV=zDfR369YcDX19pbkAu2c4bxfQ@mail.gmail.com>
Date: Tue, 5 Mar 2013 15:09:51 +0800
From: Axel Lin <axel.lin@...ics.com>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: Haojian Zhuang <haojian.zhuang@...il.com>,
"Jett.Zhou" <jtzhou@...vell.com>,
Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND 1/3] regulator: core: Add enable_is_inverted flag
to indicate set enable_mask bits to disable
2013/3/5 Mark Brown <broonie@...nsource.wolfsonmicro.com>:
> On Tue, Mar 05, 2013 at 02:16:00PM +0800, Axel Lin wrote:
>> Add enable_is_inverted flag to indicate set enable_mask bits to disable
>> when using regulator_enable_regmap and friends APIs.
>>
>> Signed-off-by: Axel Lin <axel.lin@...ics.com>
>> Reviewed-by: Haojian Zhuang <haojian.zhuang@...il.com>
>> ---
>> This patch was sent on https://lkml.org/lkml/2013/2/16/14.
>> This resend is against linux-next tree (20130305).
>
> This doesn't apply against v3.9-rc1... what are the dependencies?
I think it is because of commit 5838b032fd
"regulator: core: update kernel documentation for regulator_desc".
I found the patch (sent on https://lkml.org/lkml/2013/2/16/14 ) does not apply
to today's linux-next tree. So I re-generate the patchs against linux-next.
Should I resend the previous version of this patch?
Axel
--
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