2.6: New set of input patches

[Dmitry Torokhov]

Hi Vojtech,

I have a bunch of input patches that work quite nicely on my laptop, 
would you please consider taking them?

1. SERIO: rename serio_{register|unregister}_slave_port to
          __serio_{register|unregister}_port to better follow
          locked/lockless naming convention.

2. SERIO: There is a possibility that serio might get deleted while there
     	  are outstanding events involving that serio waiting for kseriod
          to process them. Invalidate them so kseriod thread will just
          drop dead events. (Resend)

3. Input: Introduce an optional blacklist field in input_handler structure.
          When loading a new device or a new handler try to match device
          against handler's black list before doing match on required
          attributes.
          This allows to get rid of "surprises" in connect functions, IMO
          connect should only fail when it physically can not connect, not
          because it decides it does not like device.

4. Input: Synaptics code cleanup and credit update. The switch in 
          synaptics_process_packet() was quite ugly.

5. SERIO: serio_reconnect added. Similar to serio_rescan but gives driver
          a chance to re-initialize keeping the same input device. (Resend)

6. Input/Synaptics:
   - Support for pass-through port moved from Synaptics driver to psmouse
     itself, it is cleaner and should allow using it in other drivers if
     needed.
   - The driver makes use of new reconnect functionality in serio. It will
     try to keep the same input device after resume or when it resets itself.
   - If mouse is disconnected or other mouse plugged in while sleeping the
     driver should correctly recognize that and create a new serio/input
     device. (Resend, original patch split into 2 - #4 & #6) 

Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/