linux-kernel - Re: [PATCH 1/2] regulator: Convert tps6524x to set_voltage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Mar 2012 08:52:25 +0800
From:	Axel Lin <axel.lin@...il.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, Cyril Chemparathy <cyril@...com>,
	Liam Girdwood <lrg@...com>
Subject: Re: [PATCH 1/2] regulator: Convert tps6524x to set_voltage_sel

2012/3/27 Mark Brown <broonie@...nsource.wolfsonmicro.com>:
> On Fri, Mar 23, 2012 at 07:10:28AM +0800, Axel Lin wrote:
>> Signed-off-by: Axel Lin <axel.lin@...il.com>
>
> These don't apply any more due to some of your other cleanups which got
> applied first, can you rebase please?

Hi Mark,
I tried to apply both patch to linux-next (20120326) and it looks ok.
I checked you tree and found:
Both patch are appliable to your topic/drivers branch but failed to apply
to your for-next branch.
It is because commit f03570cf "regulator: Fix setting selector in
tps6524x set_voltage function" is missing from your for-next branch. (
Note this commit already in Linus' tree, so I don't think I should
re-generate the patch against your for-next branch.)

I'm not sure if you still keep both patches, if a resend is required,
just let me know.

Thanks,
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/