From: Greg KH <greg@kroah.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>, Li Yu <raise.sail@gmail.com>,
linux-usb-devel <linux-usb-devel@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>,
Vincent Legoll <vincentlegoll@gmail.com>,
"Zephaniah E. Hull" <warp@aehallh.com>, liyu <liyu@ccoss.com.cn>
Subject: Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)
Date: Wed, 6 Dec 2006 21:16:08 -0800 [thread overview]
Message-ID: <20061207051608.GA13969@kroah.com> (raw)
In-Reply-To: <1165418317.2756.75.camel@localhost>
On Wed, Dec 06, 2006 at 04:18:37PM +0100, Marcel Holtmann wrote:
> Hi Dmitry,
>
> > > > > I still have the same objection - the "simple'" code will have to be
> > > > > compiled into the driver instead of being a separate module and
> > > > > eventyally will lead to a monster-size HID module. We have this issue
> > > > > with psmouse to a degree but with HID the growth potential is much
> > > > > bigger IMO.
> > >
> > > I guess that this paragraph wasn't for me, but rather for the author of
> > > the HID Simple Driver proposal, am I right?
> >
> > Yes, mainly for him but also for you because we need to be able to do
> > what Li Yu is trying to do and be able to tweak HID interfaces.
> >
> > ...
> >
> > > This split is quite painful, as there are many things happening in USB all
> > > the time, so the best way seem to be just to perform big split (with
> > > needed changes) at once, and then develop other things on top of it (like
> > > hidraw).
> >
> > Is there any reason why we can't mecanically move everything into
> > drivers/hid right now? Then Greg could simply forward all patches he
> > gets for HID your way and you won't have hard time merging your work
> > with others...
>
> I fully agree. Lets move and split the transports now and start the work
> on top of it. My only concern is to have a clean Git tree to the full
> history of HID changes stay intact and will trackable. Some quirk
> decisions and other stuff is not obvious and I assume will never be when
> it comes to broken HID devices.
>
> So do you have pending HID patches. If yes, please sync them with Linus
> and Jiri can setup a clean tree for the move.
I have no pending HID patches in my queue right now. Jiri, feel free to
respin your patches against Linus's tree and send them to me now. I can
handle the git stuff and send them to Linus.
thanks,
greg k-h
next prev parent reply other threads:[~2006-12-07 5:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 10:03 [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core) Li Yu
2006-12-06 10:24 ` Jiri Kosina
2006-12-06 14:24 ` Dmitry Torokhov
2006-12-06 14:38 ` Marcel Holtmann
2006-12-06 14:56 ` Dmitry Torokhov
2006-12-06 15:07 ` Marcel Holtmann
2006-12-06 15:00 ` Jiri Kosina
2006-12-06 15:13 ` Dmitry Torokhov
2006-12-06 15:18 ` Marcel Holtmann
2006-12-07 5:16 ` Greg KH [this message]
2006-12-06 15:18 ` Jiri Kosina
2006-12-06 15:25 ` Marcel Holtmann
2006-12-06 15:31 ` Dmitry Torokhov
2006-12-06 15:39 ` Jiri Kosina
2006-12-07 5:25 ` Liyu
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=20061207051608.GA13969@kroah.com \
--to=greg@kroah.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=liyu@ccoss.com.cn \
--cc=marcel@holtmann.org \
--cc=raise.sail@gmail.com \
--cc=vincentlegoll@gmail.com \
--cc=warp@aehallh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.