From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Subject: Re: [PATCH 0/11] New set of input patches
Date: Sat, 19 Jun 2004 22:17:29 -0500 [thread overview]
Message-ID: <200406192217.29206.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040619200532.GB20632@lug-owl.de>
On Saturday 19 June 2004 03:05 pm, Jan-Benedict Glaw wrote:
> On Fri, 2004-06-18 13:33:40 -0700, Dmitry Torokhov <dtor_core@ameritech.net>
> wrote in message <20040618203340.45436.qmail@web81301.mail.yahoo.com>:
> > > However, they won't apply onto Linus' tree and cause rejects in a good
> > > number of "interesting" files.
> >
> > Well, I do not consider it tested enough to be ready for Linus yet :)
> > I am thinking about publushing my input-sysfs bk tree... Will there
> > be an interest in it or you just want a patch against the vanilla 2.6.7?
> > I can do a wholesale patch but splitting my changes from other stuff in
> > Vojtech's tree does not sound very appealing...
>
> As I said, I'd love to see a -linus based patch, simply because I
> basically work with exactly this as my base. However, I can also try to
> get another base to start from.
>
Ok, how about this:
http://www.geocities.com/dt_or/input/2_6_7/
00-bk-input.patch.gz and 00-bk-sysfs.patch.gz are pulls from Vojtech's and
Greg's threes diffed against 2.6.7 - that's what I use as a baseline.
The rest of the patches are the ones that I posted earlier.
--
Dmitry
next prev parent reply other threads:[~2004-06-20 3:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 20:33 [PATCH 0/11] New set of input patches Dmitry Torokhov
2004-06-18 20:52 ` Jan-Benedict Glaw
2004-06-19 20:05 ` Jan-Benedict Glaw
2004-06-20 3:17 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 8:44 Dmitry Torokhov
2004-06-18 9:21 ` Jan-Benedict Glaw
2004-06-18 13:02 ` Dmitry Torokhov
2004-06-18 20:01 ` Jan-Benedict Glaw
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=200406192217.29206.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
/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