linux-kernel - Re: [PATCH 1/7] Input: ALPS - Move protocol information to Documentation

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: <20111031181525.GA12205@thinkpad-t410>
Date:	Mon, 31 Oct 2011 14:15:26 -0400
From:	Seth Forshee <seth.forshee@...onical.com>
To:	Chase Douglas <chase.douglas@...onical.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Alessandro Rubini <rubini@...l.unipv.it>,
	Henrik Rydberg <rydberg@...omail.se>,
	Andrew Skalski <askalski@...il.com>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/7] Input: ALPS - Move protocol information to
 Documentation

On Sun, Oct 30, 2011 at 11:33:10AM -0400, Chase Douglas wrote:
> On 10/26/2011 05:14 PM, Seth Forshee wrote:
> > In preparation for new protocol support, move the protocol
> > information currently documented in alps.c to
> > Documentation/input/alps.txt, where it can be expanded without
> > cluttering up the driver.
> > 
> > Signed-off-by: Seth Forshee <seth.forshee@...onical.com>
> 
> Makes sense. Only question is whether we should create a subdir for
> device protocols (Documentation/input/devices/alps.txt)?

That's probably a good idea if protocol documentation is going to
proliferate, but currently these docs are in Documentation/input. If we
want to move them it's a subject for a separate patch.
--
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/