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] [day] [month] [year] [list]
Message-ID: <20170718071417.umjdrk2cahnwqbz4@dell>
Date:   Tue, 18 Jul 2017 08:14:17 +0100
From:   Lee Jones <lee.jones@...aro.org>
To:     Bastien Nocera <hadess@...ess.net>
Cc:     linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mfd: intel_soc_pmic_crc: Uniquify device name

On Mon, 17 Jul 2017, Bastien Nocera wrote:

> On Mon, 2017-07-17 at 12:58 +0100, Lee Jones wrote:
> > The commit log should not be empty.
> 
> Fair.
> 
> > Please provide information as to why this change is required, etc.
> 
> SSIA.

Disagree.  The $SUBJECT says what your intention is, but does not
describe why it's required or what tangible difference it makes to a
running system.

> I also sent another patch to the same addresses labelled:
> [PATCH] gpio: crystalcove: Uniquify driver name

Okay?  I did wonder why the GPIO list was Cc'ed on this patch.

In this case the Intel guys are not listed as Maintainers for these
files, so you'll have to run ./get_maintainer.pl and pick them from
the committers entries.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ