Re: [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.

2014-12-20 Thread Samuel Thibault
Dmitry Torokhov, le Fri 19 Dec 2014 23:27:15 -0800, a écrit : > Yes, I believe it is. Good :) > Also, can you please split off input core changes from tty changes in > your patch? Yes. I this new formulation they become really completely separate matters. Samuel -- To unsubscribe from this lis

Re: [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.

2014-12-19 Thread Dmitry Torokhov
On Sat, Dec 20, 2014 at 03:16:18AM +0100, Samuel Thibault wrote: > Dmitry Torokhov, le Fri 19 Dec 2014 15:07:21 -0800, a écrit : > > On Sat, Dec 20, 2014 at 12:02:53AM +0100, Pavel Machek wrote: > > > On Fri 2014-12-19 23:59:33, Samuel Thibault wrote: > > > > Andrew Morton, le Fri 19 Dec 2014 14:46

Re: [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.

2014-12-19 Thread Samuel Thibault
Dmitry Torokhov, le Fri 19 Dec 2014 15:07:21 -0800, a écrit : > On Sat, Dec 20, 2014 at 12:02:53AM +0100, Pavel Machek wrote: > > On Fri 2014-12-19 23:59:33, Samuel Thibault wrote: > > > Andrew Morton, le Fri 19 Dec 2014 14:46:41 -0800, a écrit : > > > > > Changed in this version: > > > > > - Use k

Re: [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.

2014-12-19 Thread Dmitry Torokhov
On Sat, Dec 20, 2014 at 12:02:53AM +0100, Pavel Machek wrote: > On Fri 2014-12-19 23:59:33, Samuel Thibault wrote: > > Andrew Morton, le Fri 19 Dec 2014 14:46:41 -0800, a écrit : > > > > Changed in this version: > > > > - Use kcalloc instead of kzalloc > > > > - to avoid any mutex order violation,

Re: [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.

2014-12-19 Thread Pavel Machek
On Fri 2014-12-19 23:59:33, Samuel Thibault wrote: > Andrew Morton, le Fri 19 Dec 2014 14:46:41 -0800, a écrit : > > > Changed in this version: > > > - Use kcalloc instead of kzalloc > > > - to avoid any mutex order violation, defer LED update into a work > > > callback. > > > > Confused. This p

Re: [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.

2014-12-19 Thread Samuel Thibault
Andrew Morton, le Fri 19 Dec 2014 14:46:41 -0800, a écrit : > > Changed in this version: > > - Use kcalloc instead of kzalloc > > - to avoid any mutex order violation, defer LED update into a work callback. > > Confused. This patch is identical to the one that's presently in -mm. Well, yes: I'm

Re: [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.

2014-12-19 Thread Andrew Morton
On Wed, 10 Dec 2014 02:02:14 +0100 Samuel Thibault wrote: > This permits to reassign keyboard LEDs to something else than keyboard "leds" > state, by adding keyboard led and modifier triggers connected to a series > of VT input LEDs, themselves connected to VT input triggers, which > per-input d

Re: [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.

2014-12-09 Thread Andrew Morton
On Wed, 10 Dec 2014 08:01:00 +0100 John Crispin wrote: > Hi > > On 10/12/2014 02:02, Samuel Thibault wrote: > > This permits to reassign keyboard LEDs to something else than keyboard > > "leds" > > state, by adding keyboard led and modifier triggers connected to a series > > of VT input LEDs, t

Re: [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.

2014-12-09 Thread John Crispin
Hi On 10/12/2014 02:02, Samuel Thibault wrote: > This permits to reassign keyboard LEDs to something else than keyboard "leds" > state, by adding keyboard led and modifier triggers connected to a series > of VT input LEDs, themselves connected to VT input triggers, which > per-input device LEDs us

[PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.

2014-12-09 Thread Samuel Thibault
This permits to reassign keyboard LEDs to something else than keyboard "leds" state, by adding keyboard led and modifier triggers connected to a series of VT input LEDs, themselves connected to VT input triggers, which per-input device LEDs use by default. Userland can thus easily change the LED b