mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Jiri Kosina" <jkosina@suse.cz>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
	"Li Yu" <raise.sail@gmail.com>,
	"Greg Kroah Hartman" <greg@kroah.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 10:31:44 -0500	[thread overview]
Message-ID: <d120d5000612060731s3e1b4b6fnb8e93b970e91a852@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612061615080.29624@jikos.suse.cz>

On 12/6/06, Jiri Kosina <jkosina@suse.cz> wrote:
> On Wed, 6 Dec 2006, Dmitry Torokhov wrote:
> > 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...
>
> That definitely would be a possible solution.
>
> In fact, the patches for the split I sent to you and a few other people
> two weeks ago or so, do exactly this - in some sense "mechanical" split of
> the generic parts laying currently in USB hid, from the USB-specific ones,
> and moving them around (sure, some changes are done, like introducing data
> structures specific to usbhid, etc., but no rocket science yet).
>

If Greg is OK with that I would start with truly mechanical merge (no
now data structures, just move the files around) and merge this ASAP,
before we hit -rc1 or -rc2 at the latest. Then you can start puling up
your changesin the separate git tree.

> This would be nice to merge, if noone has any major objections, and do
> other development on top of that.
> I am currently trying to set up an account and git tree for this at
> kernel.org ... request sent, waiting for reply :)
>

Take up Marcel on his suggestion ;) I  could set up a tree too but I
am afraid I won't have enought time at the moment.

-- 
Dmitry

  parent reply	other threads:[~2006-12-06 15:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 10:03 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
2006-12-06 15:18           ` Jiri Kosina
2006-12-06 15:25             ` Marcel Holtmann
2006-12-06 15:31             ` Dmitry Torokhov [this message]
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=d120d5000612060731s3e1b4b6fnb8e93b970e91a852@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=greg@kroah.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 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®