Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932894AbbFINub (ORCPT ); Tue, 9 Jun 2015 09:50:31 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:33205 "EHLO mail-wi0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753452AbbFINuW (ORCPT ); Tue, 9 Jun 2015 09:50:22 -0400 Date: Tue, 9 Jun 2015 15:50:18 +0200 From: Pali =?utf-8?B?Um9ow6Fy?= To: Samuel Thibault , Dmitry Torokhov , Pavel Machek , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, rpurdie@rpsys.net, Greg Kroah-Hartman Subject: Re: [PATCH 0/3] Switch input leds over to standard LED class devices Message-ID: <20150609135018.GG31071@pali> References: <1433799790-31873-4-git-send-email-dmitry.torokhov@gmail.com> <1433799790-31873-3-git-send-email-dmitry.torokhov@gmail.com> <1433799790-31873-1-git-send-email-dmitry.torokhov@gmail.com> <20150609134241.GB3045@type> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150609134241.GB3045@type> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 869 Lines: 22 On Tuesday 09 June 2015 15:42:41 Samuel Thibault wrote: > Dmitry Torokhov, le Mon 08 Jun 2015 14:43:07 -0700, a écrit : > > If user wants all keyboards to light up CapsLock LED when VT state locks > > CtrlL modifier they need to write a udev rule or similar to set up > > "kbd-ctrlllock" trigger for all appearing "input%::capslock" LED class > > devices. > > I guess console-setup's maintainer will not be happy about it. I'd > say it'd be good to at least give examples how to do it in the > documentation. > What about CC relevant people who maintains those userspace packages? -- Pali Rohár pali.rohar@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/