From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] documentation: Fix pinctrl documentation for Meson8 / Meson8b
Date: Wed, 23 Mar 2016 10:20:52 -0500 [thread overview]
Message-ID: <20160323152052.GA20906@rob-hp-laptop> (raw)
In-Reply-To: <1458724440-32228-3-git-send-email-carlo@caione.org>
On Wed, Mar 23, 2016 at 10:14:00AM +0100, Carlo Caione wrote:
> From: Carlo Caione <carlo@endlessm.com>
>
> Fix pin controller documentation introducing the new compatibles for
> the pinctrl drivers specific for aobus / cbus.
>
> This is needed because we have changed the pin controller driver: we
> have now a single specialized pinctrl driver / compatible for each bus
> the controller is attached to, instead of one single driver dealing with
> all the controllers we have on different buses.
Aren't you breaking compatibility with old DTs here? If so, you need to
be clear that you are and why you think that is okay.
> Signed-off-by: Carlo Caione <carlo@endlessm.com>
> ---
> .../devicetree/bindings/pinctrl/meson,pinctrl.txt | 38 ++++------------------
> 1 file changed, 7 insertions(+), 31 deletions(-)
next prev parent reply other threads:[~2016-03-23 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 9:13 [PATCH v3 0/2] Split pinctrl device for Meson8 / Meson8b and update docs Carlo Caione
2016-03-23 9:13 ` [PATCH v3 1/2] ARM: dts: amlogic: Split pinctrl device for Meson8 / Meson8b Carlo Caione
2016-03-31 9:40 ` Linus Walleij
2016-03-23 9:14 ` [PATCH v3 2/2] documentation: Fix pinctrl documentation " Carlo Caione
2016-03-23 10:34 ` Andreas Färber
2016-03-23 15:20 ` Rob Herring [this message]
2016-03-23 16:04 ` Carlo Caione
2016-03-25 13:40 ` Rob Herring
2016-03-31 9:38 ` Linus Walleij
2016-03-31 9:41 ` Carlo Caione
2016-03-31 9:42 ` Linus Walleij
2016-03-23 19:12 ` [PATCH v3 0/2] Split pinctrl device for Meson8 / Meson8b and update docs Kevin Hilman
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=20160323152052.GA20906@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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