From: Seth Forshee <seth.forshee@canonical.com>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Alessandro Rubini <rubini@cvml.unipv.it>,
Henrik Rydberg <rydberg@euromail.se>,
Andrew Skalski <askalski@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] Input: ALPS - Move protocol information to Documentation
Date: Mon, 31 Oct 2011 14:15:26 -0400 [thread overview]
Message-ID: <20111031181525.GA12205@thinkpad-t410> (raw)
In-Reply-To: <4EAD6E36.4070502@canonical.com>
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@canonical.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.
next prev parent reply other threads:[~2011-10-31 18:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 21:14 [PATCH 0/7] Additional ALPS touchpad protocol support Seth Forshee
2011-10-26 21:14 ` [PATCH 1/7] Input: ALPS - Move protocol information to Documentation Seth Forshee
2011-10-30 15:33 ` Chase Douglas
2011-10-31 18:15 ` Seth Forshee [this message]
2011-10-26 21:14 ` [PATCH 2/7] Input: psmouse - Add PSMOUSE_CMD_RESET_WRAP Seth Forshee
2011-10-30 15:33 ` Chase Douglas
2011-10-26 21:14 ` [PATCH 3/7] Input: ALPS - Add protocol version field in alps_model_info Seth Forshee
2011-10-30 15:34 ` Chase Douglas
2011-10-26 21:14 ` [PATCH 4/7] Input: ALPS - Remove assumptions about packet size Seth Forshee
2011-10-30 15:36 ` Chase Douglas
2011-10-31 18:17 ` Seth Forshee
2011-10-31 18:24 ` Dmitry Torokhov
2011-10-31 20:01 ` Seth Forshee
2011-10-26 21:14 ` [PATCH 5/7] Input: ALPS - Add support for protocol versions 3 and 4 Seth Forshee
2011-10-30 15:37 ` Chase Douglas
2011-10-26 21:14 ` [PATCH 6/7] Input: ALPS - Add semi-MT support for v3 protocol Seth Forshee
2011-10-30 15:44 ` Chase Douglas
2011-10-26 21:14 ` [PATCH 7/7] Input: ALPS - Add documentation for protocol versions 3 and 4 Seth Forshee
2011-10-30 15:46 ` Chase Douglas
2011-10-26 21:22 ` [PATCH 0/7] Additional ALPS touchpad protocol support Chris Friesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111031181525.GA12205@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=askalski@gmail.com \
--cc=chase.douglas@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@cvml.unipv.it \
--cc=rydberg@euromail.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).