From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Input patches
Date: Tue, 20 Jul 2004 01:50:14 -0500 [thread overview]
Message-ID: <200407200150.14854.dtor_core@ameritech.net> (raw)
In-Reply-To: <200407200137.56150.dtor_core@ameritech.net>
On Tuesday 20 July 2004 01:37 am, Dmitry Torokhov wrote:
> Vojtech,
>
> Now that my driver core patches have been merged in Linus' tree I would
> like finish merging input patches. Please do:
>
> bk pull bk//dtor.bkbits.net/input
>
> You will pull the following patches (along with whatever was in Linus'
> tree as of last evening):
>
Continuing as for some reason half of the letter went into limbo...
09-mousedev-drop-attribute.packed
- drop __attribute__ ((packed)) from mousedev as we ca spare couple
of bytes to get better code readability
10-i8042-platform-device.patch
- make i8042 a platform device (instead of system) device so its
ports have a proper parent
11-serio-platform-devices.patch
- integrate ct82c710, maceps2, q40kbd and rpckbd with sysfs
as platform devices so their serio ports have proper parents
12-serio-bus-default-attr.patch
- qwitch to use bus' default device and driver attributes to
manage serio sysfs attributes
13-serio-manual-bind.patch
- allow marking serio ports (in addition to serio drivers)
as manual bind only, export the flag through sysfs:
echo -n "manual" > /sys/bus/serio/devices/serio0/bind_mode
echo -n "auto" > /sys/bus/serio/drivers/serio_raw/bind_mode
14-serio-use-driiver-find:
- use driver_find when doing manual binding, adjust refcounting as
driver_find takes a reference.
I will not be sending individual patches as they have been posted couple times
already and I'd hate spamming LKML once again.
--
Dmitry
prev parent reply other threads:[~2004-07-20 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 6:37 Input patches Dmitry Torokhov
2004-07-20 6:50 ` Dmitry Torokhov [this message]
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=200407200150.14854.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--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 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.