From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Pavel Machek" <pavel@ucw.cz>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"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: Re: [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer.
Date: Fri, 19 Dec 2014 23:59:33 +0100 [thread overview]
Message-ID: <20141219225933.GD3049@type.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <20141219144641.3a549feb1ee5f2b9400f62cb@linux-foundation.org>
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 submitting the latest version of this patch to Dmitry,
i.e. including the fixes that happened in the -mm tree.
Samuel
next prev parent reply other threads:[~2014-12-19 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 1:02 [PATCHv4] INPUT: Route keyboard LEDs through the generic LEDs layer Samuel Thibault
2014-12-10 7:01 ` John Crispin
2014-12-10 7:15 ` Andrew Morton
2014-12-19 22:46 ` Andrew Morton
2014-12-19 22:59 ` Samuel Thibault [this message]
2014-12-19 23:02 ` Pavel Machek
2014-12-19 23:07 ` Dmitry Torokhov
2014-12-20 2:16 ` Samuel Thibault
2014-12-20 7:27 ` Dmitry Torokhov
2014-12-20 9:03 ` 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=20141219225933.GD3049@type.youpi.perso.aquilenet.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=akpm@linux-foundation.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: 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;
as well as URLs for NNTP newsgroup(s).