linux-kernel - Re: Question regarding naming scheme (HP Jornada 6XX/7XX)

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: <20071126043030.GA25664@linux-sh.org>
Date:	Mon, 26 Nov 2007 13:30:30 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Kristoffer Ericson <kristoffer.ericson@...il.com>
Cc:	Dmitry <dmitry.torokhov@...il.com>,
	Russell King <linux@....linux.org.uk>,
	linux-main <linux-kernel@...r.kernel.org>
Subject: Re: Question regarding naming scheme (HP Jornada 6XX/7XX)

On Mon, Nov 26, 2007 at 12:03:29AM +0100, Kristoffer Ericson wrote:
> For instance an hp 620 user thought that their system was unsupported
> because everything was for '680'. Or the other way round 728 users
> didn't want to use 720 since they thought they would loose their extra
> ram (only difference between versions).
> 
How exactly is changing from 6XX to 600 going to change this? If users
are confused, then you should be documenting this distinction better and
working on clearing up the confusion. I'm all for making things obvious
to the end user, but there gets to be a point where it just becomes
silly.

> Why I want to use 600-series/700-series instead of 6XX/7XX is simply
> because 600-series/700-series leaves no doubt.
> 
Apparently your end users are more technically apt than I am, as I have
no idea how using 00 over XX makes things any less ambiguous.

We already have a 6xx mach-type that drivers can set their dependency on.
If it's not 680-only, then that's a perfectly reasonable dependency. Feel
free to change the Kconfig text to make the description more useful, but
please don't start idly shuffling around code and symbols because users
can't work out why a driver is available that they can't support.

Besides, the kernel frowns upon recursion, and all you need is to find
two equally confused users with differening viewpoints to hit imminent
death (whether self-inflicted or otherwise).
-
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/