All of lore.kernel.org
 help / color / mirror / Atom feed
From: samuel.thibault@ens-lyon.org (Samuel Thibault)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer
Date: Sat, 27 Dec 2014 00:21:16 +0100	[thread overview]
Message-ID: <20141226232116.GA5069@type> (raw)

Here is v5 coming, with separate patches for the kbd and the input
parts.

Samuel

WARNING: multiple messages have this Message-ID (diff)
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Pavel Machek" <pavel@ucw.cz>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"David Herrmann" <dh.herrmann@gmail.com>,
	jslaby@suse.cz, "Bryan Wu" <cooloney@gmail.com>,
	rpurdie@rpsys.net, linux-kernel@vger.kernel.org,
	"Evan Broder" <evan@ebroder.net>,
	"Arnaud Patard" <arnaud.patard@rtp-net.org>,
	"Peter Korsgaard" <jacmet@sunsite.dk>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	"Rob Clark" <robdclark@gmail.com>,
	"Niels de Vos" <devos@fedoraproject.org>,
	linux-arm-kernel@lists.infradead.org, blogic@openwrt.org,
	"Pali Rohár" <pali.rohar@gmail.com>
Subject: [PATCHv5 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer
Date: Sat, 27 Dec 2014 00:21:16 +0100	[thread overview]
Message-ID: <20141226232116.GA5069@type> (raw)

Here is v5 coming, with separate patches for the kbd and the input
parts.

Samuel

             reply	other threads:[~2014-12-26 23:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 23:21 Samuel Thibault [this message]
2014-12-26 23:21 ` [PATCHv5 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer Samuel Thibault
2014-12-26 23:21 ` [PATCHv5 1/2] INPUT: Introduce generic trigger/LED pairs between keyboard modifiers and input LEDs Samuel Thibault
2014-12-26 23:21   ` Samuel Thibault
2014-12-26 23:23 ` [PATCHv5 2/2] INPUT: Introduce generic trigger/LED pairs to " Samuel Thibault
2014-12-26 23:23   ` Samuel Thibault
2015-01-04 23:28   ` Dmitry Torokhov
2015-01-04 23:28     ` Dmitry Torokhov
2015-01-04 23:45     ` Samuel Thibault
2015-01-04 23:45       ` Samuel Thibault
2015-01-05 17:42       ` Dmitry Torokhov
2015-01-05 17:42         ` Dmitry Torokhov
2015-01-05 18:00         ` Samuel Thibault
2015-01-05 18:00           ` Samuel Thibault
2015-01-23  0:10     ` Samuel Thibault
2015-01-23  0:10       ` Samuel Thibault
2015-01-23  0:30       ` Samuel Thibault
2015-01-23  0:30         ` Samuel Thibault
2015-01-23  0:37         ` Dmitry Torokhov
2015-01-23  0:37           ` Dmitry Torokhov
2015-01-23  0:44           ` Samuel Thibault
2015-01-23  0:44             ` Samuel Thibault
2015-01-23  0:51             ` Dmitry Torokhov
2015-01-23  0:51               ` Dmitry Torokhov
2015-01-23  0:54               ` Samuel Thibault
2015-01-23  0:54                 ` Samuel Thibault
2015-01-02 19:53 ` [PATCHv5 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer Pavel Machek
2015-01-02 19:53   ` Pavel Machek
2015-01-02 20:11   ` Samuel Thibault
2015-01-02 20:11     ` Samuel Thibault
2015-01-03 19:47     ` Pavel Machek
2015-01-03 19:47       ` Pavel Machek
2015-01-21 15:21   ` Samuel Thibault
2015-01-21 15:21     ` Samuel Thibault
2015-01-23 12:31     ` Samuel Thibault
2015-01-23 12:31       ` Samuel Thibault

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=20141226232116.GA5069@type \
    --to=samuel.thibault@ens-lyon.org \
    --cc=linux-arm-kernel@lists.infradead.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 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.