From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/19] New set of input patches
Date: Tue, 29 Jun 2004 09:25:50 +0200 [thread overview]
Message-ID: <20040629072550.GA1238@ucw.cz> (raw)
In-Reply-To: <200406290201.28433.dtor_core@ameritech.net>
On Tue, Jun 29, 2004 at 02:01:28AM -0500, Dmitry Torokhov wrote:
> On Monday 28 June 2004 10:07 am, Vojtech Pavlik wrote:
> > On Mon, Jun 28, 2004 at 07:54:53AM -0700, Dmitry Torokhov wrote:
> > >
> > > Sysfs changes should be useable even without platform device changes
> > > and I would like start syncing with you. Would you take patches 2
> > > through 10 (I will drop the legacy_position stuff)?
> >
> > Yes.
> >
>
> Vojtech,
>
> As we discussed I dropped the legacy_position sysfs attribute and moved
> patches 2 through 10 to my repository on bkbits.net. I also moved patch
> #14 because sa1111ps2, gscps2, ambakmi and pcips2 have already been
> integrated with sysfs so linking their serio ports to their devices
> are simple one-liners not depending on anything I sent to Greg.
>
> Please do:
>
> bk pull bk://dtor.bkbits.net/input
Thanks!
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-06-29 7:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 14:54 [PATCH 0/19] New set of input patches Dmitry Torokhov
2004-06-28 15:07 ` Vojtech Pavlik
2004-06-29 7:01 ` Dmitry Torokhov
2004-06-29 7:25 ` Vojtech Pavlik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-28 10:05 Sau Dan Lee
2004-06-28 5:08 Dmitry Torokhov
2004-06-28 6:52 ` Vojtech Pavlik
2004-06-28 7:13 ` Dmitry Torokhov
2004-06-28 7:51 ` Vojtech Pavlik
2004-06-28 10:32 ` Neil Brown
2004-06-28 12:13 ` Vojtech Pavlik
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=20040629072550.GA1238@ucw.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--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