lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <555DDF94.5040006@samsung.com>
Date:	Thu, 21 May 2015 15:37:24 +0200
From:	Jacek Anaszewski <j.anaszewski@...sung.com>
To:	Stas Sergeev <stsp@...t.ru>
Cc:	linux-leds@...r.kernel.org,
	Linux kernel <linux-kernel@...r.kernel.org>,
	Stas Sergeev <stsp@...rs.sourceforge.net>,
	Bryan Wu <cooloney@...il.com>,
	Richard Purdie <rpurdie@...ys.net>,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: [PATCH 01/20] leds: implement LED_BRIGHTNESS_FAST flag

On 05/21/2015 03:27 PM, Stas Sergeev wrote:
> 21.05.2015 16:22, Jacek Anaszewski пишет:
>> Hi Stas,
>>
>> My intention was to add a developer of each driver on
>> cc in the commit message.
> I did. You can see CC: Chris Boot <bootc@...tc.net> at patch 12.
> Otherwise, this is all the get_maintainers.pl script gives me.
> So unless you can suggest some other script, or get_maintainers.pl
> is fixed, what do you expect me to do?

You don't have to rely on get_maintainers.pl script only, but
you can obtain the authors' names from driver headers or
MODULE_AUTHOR entries at the bottom.

> Anyway. I can reduce the patchset to just the initial patch and
> the leds-gpio one. In a hope others will change more drivers later.
> At least that would be trivial to review and apply.
> Deal?

Please don't reduce it. The greater number of people familiar with
related drivers/devices will get this, the greater chance that we
won't miss something crucial.

-- 
Best Regards,
Jacek Anaszewski
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ