From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751433AbdGRHOW (ORCPT ); Tue, 18 Jul 2017 03:14:22 -0400 Received: from mail-wr0-f178.google.com ([209.85.128.178]:34480 "EHLO mail-wr0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751353AbdGRHOV (ORCPT ); Tue, 18 Jul 2017 03:14:21 -0400 Date: Tue, 18 Jul 2017 08:14:17 +0100 From: Lee Jones To: Bastien Nocera Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mfd: intel_soc_pmic_crc: Uniquify device name Message-ID: <20170718071417.umjdrk2cahnwqbz4@dell> References: <20170620163323.16345-1-hadess@hadess.net> <20170717115829.2mp2eyodrcdqy4t5@dell> <1500297840.24690.4.camel@hadess.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1500297840.24690.4.camel@hadess.net> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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