From: Samuel Thibault <samuel.thibault@ens-lyon.org> To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>, "Pali Rohár" <pali.rohar@gmail.com>, "Pavel Machek" <pavel@ucw.cz>, "David Herrmann" <dh.herrmann@gmail.com>, "Jiri Slaby" <jslaby@suse.cz>, "Bryan Wu" <cooloney@gmail.com>, "Richard Purdie" <rpurdie@rpsys.net>, lkml <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" <linux-arm-kernel@lists.infradead.org>, blogic@openwrt.org Subject: Re: [PATCHv7 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer Date: Thu, 25 Jun 2015 17:30:32 +0200 [thread overview] Message-ID: <20150625153032.GE3093@type.bordeaux.inria.fr> (raw) In-Reply-To: <20150605152806.GE2267@type> Hello, Just to give an update to people who where Cc-ed at some point in the discussion: a version reworked by Dmitry got pulled into Linus' tree, so it should get into 4.2! Thanks to everybody involved, Samuel
WARNING: multiple messages have this Message-ID (diff)
From: samuel.thibault@ens-lyon.org (Samuel Thibault) To: linux-arm-kernel@lists.infradead.org Subject: [PATCHv7 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer Date: Thu, 25 Jun 2015 17:30:32 +0200 [thread overview] Message-ID: <20150625153032.GE3093@type.bordeaux.inria.fr> (raw) In-Reply-To: <20150605152806.GE2267@type> Hello, Just to give an update to people who where Cc-ed at some point in the discussion: a version reworked by Dmitry got pulled into Linus' tree, so it should get into 4.2! Thanks to everybody involved, Samuel
next prev parent reply other threads:[~2015-06-25 15:30 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-17 19:15 [PATCHv7 0/2] INPUT: Route keyboard LEDs through the generic LEDs layer Samuel Thibault 2015-02-17 19:15 ` Samuel Thibault 2015-04-01 20:00 ` Pali Rohár 2015-04-01 20:00 ` Pali Rohár 2015-04-01 21:11 ` Samuel Thibault 2015-04-01 21:11 ` Samuel Thibault 2015-04-02 14:44 ` Pavel Machek 2015-04-02 14:44 ` Pavel Machek 2015-04-12 22:16 ` Pali Rohár 2015-04-12 22:16 ` Pali Rohár 2015-04-13 8:06 ` Samuel Thibault 2015-04-13 8:06 ` Samuel Thibault 2015-04-23 16:55 ` Pali Rohár 2015-04-23 16:55 ` Pali Rohár 2015-04-23 17:04 ` Dmitry Torokhov 2015-04-23 17:04 ` Dmitry Torokhov 2015-05-02 22:44 ` Pali Rohár 2015-05-02 22:44 ` Pali Rohár 2015-06-05 15:28 ` Samuel Thibault 2015-06-05 15:28 ` Samuel Thibault 2015-06-25 15:30 ` Samuel Thibault [this message] 2015-06-25 15:30 ` Samuel Thibault 2015-06-25 15:37 ` Peter Korsgaard 2015-06-25 15:37 ` Peter Korsgaard 2015-06-25 16:25 ` Samuel Thibault 2015-06-25 16:25 ` Samuel Thibault 2015-06-25 16:53 ` Dmitry Torokhov 2015-06-25 16:53 ` Dmitry Torokhov 2015-06-26 8:09 ` Pali Rohár 2015-06-26 8:09 ` Pali Rohár
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=20150625153032.GE3093@type.bordeaux.inria.fr \ --to=samuel.thibault@ens-lyon.org \ --cc=arnaud.patard@rtp-net.org \ --cc=blogic@openwrt.org \ --cc=cooloney@gmail.com \ --cc=devos@fedoraproject.org \ --cc=dh.herrmann@gmail.com \ --cc=dmitry.torokhov@gmail.com \ --cc=evan@ebroder.net \ --cc=jacmet@sunsite.dk \ --cc=jslaby@suse.cz \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=pali.rohar@gmail.com \ --cc=pavel@ucw.cz \ --cc=robdclark@gmail.com \ --cc=rpurdie@rpsys.net \ --cc=s.hauer@pengutronix.de \ /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: linkBe 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.