From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Pawel Moll <pawel.moll@arm.com>,
Rob Herring <rob.herring@calxeda.com>,
Ian Campbell <ian.campbell@citrix.com>,
Mark Rutland <mark.rutland@arm.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH 1/2] pinctrl: clean up pinconfig-generic documentation
Date: Wed, 7 Aug 2013 21:32:34 +0200 [thread overview]
Message-ID: <CACRpkdb1qSO2OhFebgAPESAzRySaCyQcBH97s4E7+F-3wmXZpw@mail.gmail.com> (raw)
In-Reply-To: <1375739760-18833-1-git-send-email-swarren@wwwdotorg.org>
On Mon, Aug 5, 2013 at 11:55 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Reword the section of pinctrl-bindings.txt that describes generic
> properties that pinctrl bindings may use. The aim is to make the text
> clearer, and more explicitly call out the responsibility of individual
> bindings that use the generic properties to define which of the
> properties are used, and how.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> LinusW, Laxman, this is the binding doc cleanup I mentioned I was going
> to send when reviewing Laxman's Palmas pinctrl driver.
Looks good to me.
Patch applied.
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-08-07 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 21:55 [PATCH 1/2] pinctrl: clean up pinconfig-generic documentation Stephen Warren
2013-08-05 21:56 ` [PATCH 2/2] pinctrl: add generic pins and functions properties Stephen Warren
2013-08-06 8:41 ` Mark Rutland
2013-08-06 17:01 ` Stephen Warren
2013-08-07 19:32 ` Linus Walleij [this message]
2013-08-07 19:41 ` [PATCH 1/2] pinctrl: clean up pinconfig-generic documentation Stephen Warren
2013-08-07 19:54 ` 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=CACRpkdb1qSO2OhFebgAPESAzRySaCyQcBH97s4E7+F-3wmXZpw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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).