From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Pavel Machek" <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH V4 1/6] Minimal changes to the core input system
Date: Wed, 5 Nov 2008 16:51:31 -0500 [thread overview]
Message-ID: <9e4733910811051351r3682dc1erc67d04d92142c4e2@mail.gmail.com> (raw)
In-Reply-To: <20081105213828.GA3966@elf.ucw.cz>
On Wed, Nov 5, 2008 at 4:38 PM, Pavel Machek <pavel@suse.cz> wrote:
> On Wed 2008-11-05 14:47:38, Jon Smirl wrote:
>> Minimal changes to the core input system. The bulk of IR support loads as a module. These changes are passive if the rest of IR isn't loaded.
>>
>> Jon Smirl
>> <jonsmirl@gmail.com>
>
> Apart from too long lines in changelog and missed Signed-off-by: it
> looks okay to me ;-).
I'm not looking to get it into the kernel yet, it still needs some
more eyes looking at it to make sure the API are ok.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-11-05 21:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 19:47 [RFC PATCH V4 0/6] In-kernel IR remote control support Jon Smirl
2008-11-05 19:47 ` [RFC PATCH V4 1/6] Minimal changes to the core input system Jon Smirl
2008-11-05 21:38 ` Pavel Machek
2008-11-05 21:51 ` Jon Smirl [this message]
2008-11-05 19:47 ` [RFC PATCH V4 2/6] Core IR module Jon Smirl
2008-11-05 19:47 ` [RFC PATCH V4 3/6] Configfs support for IR Jon Smirl
2008-11-05 21:41 ` Pavel Machek
2008-11-05 21:51 ` Jon Smirl
2008-11-05 19:47 ` [RFC PATCH V4 4/6] GPT driver for in-kernel IR support Jon Smirl
2008-11-05 19:47 ` [RFC PATCH V4 5/6] Example of PowerPC device tree support for GPT based IR Jon Smirl
2008-11-05 19:47 ` [RFC PATCH V4 6/6] Microsoft mceusb2 driver for in-kernel IR subsystem Jon Smirl
2008-11-05 19:59 ` [RFC PATCH V4 0/6] In-kernel IR remote control support J.R. Mauro
2008-11-05 20:07 ` Jon Smirl
2008-11-05 20:15 ` J.R. Mauro
2008-11-05 20:47 ` Jon Smirl
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=9e4733910811051351r3682dc1erc67d04d92142c4e2@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®