Thread (9 messages) 9 messages, 3 authors, 2016-05-20

Re: [PATCH 1/2 V3] dt: add Atmel Captouch bindings

From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: 2016-05-20 16:16:09
Also in: linux-input, lkml

On Fri, May 20, 2016 at 07:56:51AM -0500, Rob Herring wrote:
On Wed, May 18, 2016 at 4:59 PM, Dmitry Torokhov
[off-list ref] wrote:
quoted
On Wed, May 18, 2016 at 11:44:04AM -0500, Rob Herring wrote:
quoted
On Mon, May 16, 2016 at 01:54:53PM -0700, Grant Grundler wrote:
quoted
From: Daniel Hung-yu Wu <redacted>

Add binding for Atmel Capacitive Touch Button device.

Signed-off-by: Daniel Hung-yu Wu <redacted>
Signed-off-by: Grant Grundler <redacted>
---
 .../devicetree/bindings/input/atmel,captouch.txt   | 36 ++++++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/input/atmel,captouch.txt
Acked-by: Rob Herring <robh@kernel.org>
Folded into the driver patch and applied.
Folded why? Please don't do that. You should be committing what is
posted as is for the most part. We specifically ask that binding
changes are kept separate commits. It also messes up the ability to
I know that you ask for binding docs to be posted separately (I guess
so that devicetree list is not overrun with driver code mails), but
logically driver patch and binding doc patch are a single change and
should be committed together, so that when I am researching the history
I can easily see what was introduced and when. You do not require header
changes to be submitted separately form .c files, do you?
correlate git commits to patchworks or mail searches.
The fact that it was applied can be found in mail archives.

Thanks.

-- 
Dmitry
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help