From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Michael Hanselmann <linux-kernel@hansmi.ch>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
linux-kernel@vger.kernel.org,
linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: usb/input: Split into separate layers (was: Re: [PATCH 1/1] usb/input: Add missing keys to hid-debug.h)
Date: Wed, 4 Jan 2006 02:10:31 -0500 [thread overview]
Message-ID: <200601040210.31849.dtor_core@ameritech.net> (raw)
In-Reply-To: <20060103221133.GA13921@hansmi.ch>
On Tuesday 03 January 2006 17:11, Michael Hanselmann wrote:
> Hello Vojtech
>
> On Tue, Jan 03, 2006 at 08:53:44PM +0100, Vojtech Pavlik wrote:
> > We should split HID in two parts - transport and decoding. This would
> > help in many places:
> > [...]
>
> > I don't have the time to do the split myself, but it shouldn't be too
> > hard.
>
> And for myself, I think I'm not enough into kernel development already.
> Beside of that, USB isn't my very interest but those patches had to be
> done to get the new PowerBook models running smooth. Hopefully there's
> someone else interested in doing the split because it would be a good
> thing.
>
> > It would not be the perfect solution for Apple keyboards, [...]
>
> Does that mean the patch doesn't get into the kernel until the split
> happened?
>
No, it does not mean that.
--
Dmitry
next prev parent reply other threads:[~2006-01-04 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 23:37 [PATCH 1/1] usb/input: Add missing keys to hid-debug.h Michael Hanselmann
2006-01-03 6:42 ` Dmitry Torokhov
2006-01-03 19:53 ` Vojtech Pavlik
2006-01-03 22:11 ` usb/input: Split into separate layers (was: Re: [PATCH 1/1] usb/input: Add missing keys to hid-debug.h) Michael Hanselmann
2006-01-04 7:10 ` Dmitry Torokhov [this message]
2006-01-04 10:34 ` Vojtech Pavlik
2006-01-05 0:24 ` [PATCH 1/1] usb/input: Add missing keys to hid-debug.h Marcel Holtmann
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=200601040210.31849.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@hansmi.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@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