linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
	"robh@kernel.org" <robh@kernel.org>
Cc: Philippe Schenker <philippe.schenker@toradex.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-imx@nxp.com" <linux-imx@nxp.com>
Subject: Re: [PATCH v2 3/5] dt-bindings: input: tochscreen: ad7879: generic node names in example
Date: Wed, 6 Nov 2019 08:58:25 +0000	[thread overview]
Message-ID: <c200444ba450d7884cd26e12163b68db6db63725.camel@toradex.com> (raw)
In-Reply-To: <20191030231205.GI57214@dtor-ws>

On Wed, 2019-10-30 at 16:12 -0700, Dmitry Torokhov wrote:
> On Wed, Oct 30, 2019 at 09:04:55AM -0500, Rob Herring wrote:
> > On Sat, Oct 26, 2019 at 11:04:01AM +0200, Marcel Ziswiler wrote:
> > > From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> > 
> > There's a typo in the subject.
> 
> I fixed it up file applying, thank you for noticing.

Where exactly did you apply this? As I still can't find it applied
anywhere. Thanks!

> > > Update example in ad7879 devicetree documentation to use generic
> > > touch
> > > controller node names.
> > > 
> > > Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> > > 
> > > ---
> > > 
> > > Changes in v2: New patch.
> > > 
> > >  .../devicetree/bindings/input/touchscreen/ad7879.txt          |
> > > 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)

  reply	other threads:[~2019-11-06  8:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26  9:03 [PATCH v2 1/5] arm: dts: vf-colibri: fix typo in top-level module compatible Marcel Ziswiler
2019-10-26  9:04 ` [PATCH v2 2/5] dt-bindings: arm: fsl: add nxp based toradex apalis/colibri binding docu Marcel Ziswiler
2019-10-30 14:03   ` Rob Herring
2019-11-04  1:25   ` Shawn Guo
2019-10-26  9:04 ` [PATCH v2 3/5] dt-bindings: input: tochscreen: ad7879: generic node names in example Marcel Ziswiler
2019-10-30 14:04   ` Rob Herring
2019-10-30 14:04   ` Rob Herring
2019-10-30 23:12     ` Dmitry Torokhov
2019-11-06  8:58       ` Marcel Ziswiler [this message]
2019-11-12  0:05         ` dmitry.torokhov
2019-10-26  9:04 ` [PATCH v2 4/5] arm64: dts: freescale: add initial support for colibri imx8x Marcel Ziswiler
2019-10-26  9:04 ` [PATCH v2 5/5] dt-bindings: arm: fsl: add nxp based toradex colibri-imx8x binding docu Marcel Ziswiler
2019-10-30 14:05   ` Rob Herring
2019-11-04  1:26   ` Shawn Guo
2019-11-04  1:16 ` [PATCH v2 1/5] arm: dts: vf-colibri: fix typo in top-level module compatible Shawn Guo
2019-11-04  1:20   ` Shawn Guo
2019-11-04  1:29     ` Shawn Guo
2019-11-04  6:51       ` Marcel Ziswiler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c200444ba450d7884cd26e12163b68db6db63725.camel@toradex.com \
    --to=marcel.ziswiler@toradex.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=philippe.schenker@toradex.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).