linux-kernel - Re: [PATCH] regulator: core: use regulator name for sysfs

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: <51267454.5040607@wwwdotorg.org>
Date:	Thu, 21 Feb 2013 12:24:04 -0700
From:	Stephen Warren <swarren@...dotorg.org>
To:	Shawn Joo <sjoo@...dia.com>
CC:	broonie@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: core: use regulator name for sysfs

On 02/21/2013 12:53 AM, Shawn Joo wrote:
> regulator is named by numbering on sysfs, e.g. regulator.0, regulator.1
> it confuses to find desired regulator before counting the order.
> add option for regulator name by use_name_onsysfs.
> if it is true and name is not NULL, desc's name will be the name.
> e.g. if name in desc is "LDO0", then regulator.LDO0 on sysfs.
> otherwise it follows origin.

Does it make sense to make this change always, rather than based on some
new flag in regulator_desc?

Another place a similar change might be useful is debugfs.
--
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/