linux-kernel - Re: [PATCH 1/5] regulator: tps65090: rename driver name and regulator name

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]

Message-ID: <50726BE0.3020904@nvidia.com>
Date:	Mon, 8 Oct 2012 11:30:00 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Venu Byravarasu <vbyravarasu@...dia.com>
CC:	"broonie@...nsource.wolfsonmicro.com" 
	<broonie@...nsource.wolfsonmicro.com>, "lrg@...com" <lrg@...com>,
	"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
	"axel.lin@...il.com" <axel.lin@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/5] regulator: tps65090: rename driver name and regulator
 name

On Monday 08 October 2012 11:23 AM, Venu Byravarasu wrote:
>> -----Original Message-----
>> From: Laxman Dewangan
>> Sent: Saturday, October 06, 2012 8:48 PM
>>
>>   static struct platform_driver tps65090_regulator_driver = {
>>   	.driver	= {
>> -		.name	= "tps65090-regulator",
>> +		.name	= "tps65090-pmic",
> As the driver itself is regulator driver, why should we rename it to pmic?
>

I observed that other drivers are using the similar names 
<chip_name>-pmic and so with inline with others.
--
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/