linux-kernel - Re: lanana: Add major/minor entries for PPC QE UART devices

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: <47493f913dddbec5e420bd7434709291@kernel.crashing.org>
Date:	Wed, 28 Feb 2007 20:45:07 +0100
From:	Segher Boessenkool <segher@...nel.crashing.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-ppc-embedded <linuxppc-embedded@...abs.org>,
	Timur Tabi <timur@...escale.com>,
	Dan Malek <dan@...eddedalley.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Torben.Mathiasen@...com
Subject: Re: lanana: Add major/minor entries for PPC QE UART devices

>> Another option is to use 46..49 for UARTs #0..3,
>> and 192..195 for UARTs #4..7.
>> Or, perhaps better, use 46..49 for #0..3, and
>> 192..199 for #0..7, handling the duplication in
>> the driver; and deprecate the old range.
>
> That sounds like more hassle than it's worth.  The discontinuous range 
> may be annoying, but it isn't really a huge amount of code.

Yeah.  My suggestion would allow to get rid of that
extra code some day, though (but sure, is that worth
it?)


Segher

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