public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/9] New set of input patches
Date: Tue, 11 May 2004 01:24:14 -0500	[thread overview]
Message-ID: <200405110124.14948.dtor_core@ameritech.net> (raw)

Hi Vojtech,

I have some more input patches. Nothing too intresting, most of the important
stuff has been posted on LKML before. Here they are:

01-serio-whitespace.patch:
	trailing whitespace fixes in drivers/input/serio

02-kbd98io-interrupt.patch:
	kbd98io_interrupt should return irqreturn_t

03-kdb98-interrupt.patch:
	kbd98_interrupt should return irqreturn_t

04-h3600-fixes.patch:
	various fixes for H3600 touchscreen driver
         - h3600ts_interrupt, npower_button_handler and action_button_handler
           should return irqreturn_t
         - fix missing argument in h3600ts_process_packet call
         - add MODULE_AUTHOR, MODULE_DESCRIPTION and MODULE_LICENSE
         - small formatting changes
	It still does not compile because of bad PM_ constants though

05-twidjoy-fixes.patch:
         - twidjoy_interrupt should return irqreturn_t
         - add MODULE_DESCRIPTION and MODULE_LICENSE

06-keyboard-whitespace.patch:
	trailing whitespace fixes in drivers/input/keyboard

07-power-license.patch:
	power - add MODULE_LICENSE

08-joystick-whitespace.patch:
	trailing whitespace fixes in drivers/input/joystick

09-gameport-whitespace.patch:
	trailing whitespace fixes in drivers/input/gameport

10-input-whitespace.patch:
	trailing whitespace fixes in drivers/input

11-synaptics-reconnect.patch:
	do not call synaptics_init unless we are ready to do full
        mouse setup or we can oops on resume

12-i8042-interrupt.patch:
	split i8042 interrupt handling into an IRQ handler and a tasklet,
	as with mousedev, evdev and so on we were doing too much work in
	IRQ context

13-i8042-unload.patch:
	Patch from Sau Dan Lee
  	Kill the timer only after removing interrupt handler,
        otherwise there is a chance that interrupt handler will install
        the timer again and it will trigger after module is unloaded.

14-mousedev-multiplexing.patch:
	better multiplex absolute and relative devices; cleanups

I did merge with Linus' tree to resolve conflicts with Eric's latest
changes to logips2pp (hope he does not mind). Please do:
bk pull bk://dtor.bkbits.net/input

The following patches are against your tree rather then Linis' and I will
not post whitespace fixing patches as they are too boring...

There is also a cumulative patch agains Linus' tree at:
http://www.geocities.com/dt_or/input/2_6_6/input-cumulative.patch.gz

-- 
Dmitry

             reply	other threads:[~2004-05-11  6:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11  6:24 Dmitry Torokhov [this message]
2004-05-11  9:01 ` [PATCH 0/9] New set of input patches Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2004-02-29 14:57 Dmitry Torokhov
2004-02-29  6:53 Dmitry Torokhov
2004-03-02 13:02 ` Vojtech Pavlik
2004-03-02 17:45   ` Dmitry Torokhov

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=200405110124.14948.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox