linux-kernel - Re: [PATCH] regulator: tps6586x: correct vin pin for sm0/sm1/sm2

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 08 Aug 2012 15:57:04 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	broonie@...nsource.wolfsonmicro.com
CC:	Laxman Dewangan <ldewangan@...dia.com>, lrg@...com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: tps6586x: correct vin pin for sm0/sm1/sm2

On 07/24/2012 02:18 AM, Laxman Dewangan wrote:
> As per datasheet, the vin pin for the regulator is named
> as vin_sm0, vin_sm1, vin_sm2 for sm0, sm1 and sm2 respectively.
> 
> Correcting the names in driver and documentation to match with
> datasheet.

Mark,

This patch was in next-20120803, but seems to have been dropped from
next-20120806 and later:

> git log next-20120803 --oneline -- drivers/regulator/tps6586x-regulator.c|cat
> c7bc4e5 regulator: tps6586x: correct vin pin for sm0/sm1/sm2
> 7c7fac3 regulator: tps6586x: add support for input supply
> f464703 regulator: tps6586x: Convert to regulator_list_voltage_table

> git log next-20120806 --oneline -- drivers/regulator/tps6586x-regulator.c|cat
> 4c79c8d regulator: tps6586x: Convert to regulator_[enable|disable|is_enabled|get_voltage_sel]_regmap
> 7c7fac3 regulator: tps6586x: add support for input supply
> f464703 regulator: tps6586x: Convert to regulator_list_voltage_table

I assume that was just an accident?

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