From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754184AbaCJQgI (ORCPT ); Mon, 10 Mar 2014 12:36:08 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:43251 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753475AbaCJQgE (ORCPT ); Mon, 10 Mar 2014 12:36:04 -0400 Date: Mon, 10 Mar 2014 16:35:57 +0000 From: Lee Jones To: Dmitry Torokhov Cc: Gabriel FERNANDEZ , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Rob Landley , Russell King , Grant Likely , devicetree@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-input@vger.kernel.org, kernel@stlinux.com, Giuseppe Condorelli Subject: Re: [PATCH 1/5] drivers: input: keyboard: st-keyscan: add keyscan driver Message-ID: <20140310163557.GJ13661@lee--X1> References: <1393990772-9567-1-git-send-email-gabriel.fernandez@st.com> <1393990772-9567-2-git-send-email-gabriel.fernandez@st.com> <20140310114819.GO14976@lee--X1> <20140310152859.GA29054@core.coreip.homeip.net> <20140310153815.GE13661@lee--X1> <20140310155824.GB29054@core.coreip.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20140310155824.GB29054@core.coreip.homeip.net> 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 > > > > > This patch adds ST Keyscan driver to use the keypad hw a subset > > > > > of ST boards provide. Specific board setup will be put in the > > > > > given dt. > > > > > > > > > > Signed-off-by: Giuseppe Condorelli > > > > > Signed-off-by: Gabriel Fernandez > > > > > > > > Are you sure these are in the correct order? > > > > > > > > What is the history of this commit? > > > > > > > > > --- > > > > > .../devicetree/bindings/input/st-keypad.txt | 50 ++++ > > > > > > > > This should be submitted as a seperate patch. > > > > > > Why do we have such requirement? To me it would make more sense to add > > > binding documentation in the same commit as the code that uses these > > > bindings. > > > > I'm inclined to agree with you and that's actually how we used to do > > it, but a decision was made by the DT guys at one of the Kernel > > Summits to submit Documentation as a separate patch. > > Do you have background for this decision? To me it is akin splitting > header file into a separate patch. The discussion/decision was verbal unfortunately. I don't really mind either way. I'm just attempting to enforce the decisions that were made by the forces-that-be. Perhaps ping devicetree@vger.kernel.org with me in CC for more clarification if required. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog