linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
	gregkh@linuxfoundation.org, linus.walleij@linaro.org,
	driverdev-devel@linuxdriverproject.org,
	Sergio Paracuellos <sergio.paracuellos@gmail.com>,
	neil@brown.name
Subject: Re: [PATCH 2/2] dt-bindings: document gpio-mt7621 bindings
Date: Wed, 13 Jun 2018 12:40:00 +0300	[thread overview]
Message-ID: <20180613094000.m7x7l7lpccf7yqm3@mwanda> (raw)
In-Reply-To: <20180612205638.GA2404@rob-hp-laptop>

On Tue, Jun 12, 2018 at 02:56:38PM -0600, Rob Herring wrote:
> Bindings are for h/w, not a driver.
> 
> > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> > Reviewed-by: NeilBrown <neil@brown.name>
> 
> Space              ^

Pretty sure that was deliberate...  Otherwise he's been making that
same mistake for over a decade now.

regards,
dan carpenter

  reply	other threads:[~2018-06-13  9:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-02  7:30 [PATCH 0/2] gpio: mediatek: driver for gpio chip in MT7621 SoC Sergio Paracuellos
2018-06-02  7:30 ` [PATCH 1/2] gpio: mediatek: add driver for MT7621 Sergio Paracuellos
2018-06-08 11:59   ` Linus Walleij
2018-06-08 12:17     ` Linus Walleij
2018-06-09  6:17       ` Sergio Paracuellos
2018-06-09  5:54     ` Sergio Paracuellos
2018-06-11  3:29     ` Sean Wang
2018-06-02  7:30 ` [PATCH 2/2] dt-bindings: document gpio-mt7621 bindings Sergio Paracuellos
2018-06-12 20:56   ` Rob Herring
2018-06-13  9:40     ` Dan Carpenter [this message]
2018-06-13 16:23     ` Sergio Paracuellos
2018-06-13 19:28       ` Rob Herring
2018-06-14  4:45         ` Sergio Paracuellos
2018-06-14 14:17           ` Linus Walleij
2018-06-14 16:20             ` Sergio Paracuellos
2018-06-14 14:14         ` Linus Walleij
2018-06-14 14:33           ` Rob Herring
2018-06-14 14:48             ` Linus Walleij

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=20180613094000.m7x7l7lpccf7yqm3@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devicetree@vger.kernel.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=robh@kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    /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).