From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Martyn Welch <martyn.welch@ge.com>,
linux-input@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v3] powerpc: Add i8042 keyboard and mouse irq parsing
Date: Wed, 02 Jun 2010 17:25:32 +1000 [thread overview]
Message-ID: <1275463532.1931.773.camel@pasglop> (raw)
In-Reply-To: <20100602062634.GA3713@core.coreip.homeip.net>
On Tue, 2010-06-01 at 23:26 -0700, Dmitry Torokhov wrote:
>
> FYI: i8042 core expects I8042_{KBD|AUX}_IRQ to be integers, however it
> is certainly fixable...
Let's not bother.
Cheers,
Ben.
prev parent reply other threads:[~2010-06-02 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 8:09 [PATCH v3] powerpc: Add i8042 keyboard and mouse irq parsing Martyn Welch
2010-05-25 20:21 ` Grant Likely
2010-05-25 23:19 ` Mitch Bradley
2010-05-29 3:35 ` Benjamin Herrenschmidt
2010-05-29 3:35 ` Benjamin Herrenschmidt
2010-06-01 12:41 ` Martyn Welch
2010-06-02 6:26 ` Dmitry Torokhov
2010-06-02 7:25 ` Benjamin Herrenschmidt [this message]
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=1275463532.1931.773.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=martyn.welch@ge.com \
/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).