linux-kernel - Re: [PATCH] rtc: Group Kconfig entries by vendor

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:	Wed, 4 Nov 2015 08:06:28 -0800
From:	Sören Brinkmann <soren.brinkmann@...inx.com>
To:	Alexandre Belloni <alexandre.belloni@...e-electrons.com>
CC:	Alessandro Zummo <a.zummo@...ertech.it>,
	<rtc-linux@...glegroups.com>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] rtc: Group Kconfig entries by vendor

Hi Alexandre,

On Wed, 2015-11-04 at 10:25AM +0100, Alexandre Belloni wrote:
> On 03/11/2015 at 23:13:46 -0800, Soren Brinkmann wrote :
> > The RTC entries are mostly grouped by vendor. Move the few outliers in
> > place.
> > Also, change the one occurrence of 'nxp' to 'NXP' to make all NXP
> > entries consistent.
> > 
> 
> Yeah, I've been contemplating reordering the Kconfig, the main issue
> being that Philips and NXP is the same entity. And also, we have RTCs
> manufactured by different vendors that use the same chip
> (Abracon/Epson/Philips/Microcrystal) so I'm not sure what is clearer for
> the end user :)

Yeah, I wasn't sure if this is wanted or how far to go. It was mainly
triggered by the NXP devices that weren't grouped and differed in
capitalization. From there I took it a little further. Just let met know if
you want this somewhat different or not at all. It's just a suggestion
and I find it helpful if things are somewhat ordered (I was thinking go
full alphabetical sorting but didn't want to go that far without another
opinion). But I'm fine either way.

	Thanks,
	Sören

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