From: Rob Herring <robh@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Stephan Gerhold <stephan@gerhold.net>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: mfd: ab8500: Document AB8505 bindings
Date: Tue, 3 Dec 2019 15:40:19 -0600 [thread overview]
Message-ID: <20191203214019.GA24180@bogus> (raw)
In-Reply-To: <20191117221053.278415-1-stephan@gerhold.net>
On Sun, 17 Nov 2019 23:10:52 +0100, Stephan Gerhold wrote:
> AB8505 can now be configured from the device tree.
> The configuration is almost identical to AB8500, so just add a note
> for the nodes/compatibles that differ between the two revisions.
>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
> Documentation/devicetree/bindings/mfd/ab8500.txt | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Lee Jones <lee.jones@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Stephan Gerhold <stephan@gerhold.net>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 1/2] dt-bindings: mfd: ab8500: Document AB8505 bindings
Date: Tue, 3 Dec 2019 15:40:19 -0600 [thread overview]
Message-ID: <20191203214019.GA24180@bogus> (raw)
In-Reply-To: <20191117221053.278415-1-stephan@gerhold.net>
On Sun, 17 Nov 2019 23:10:52 +0100, Stephan Gerhold wrote:
> AB8505 can now be configured from the device tree.
> The configuration is almost identical to AB8500, so just add a note
> for the nodes/compatibles that differ between the two revisions.
>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
> Documentation/devicetree/bindings/mfd/ab8500.txt | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-12-03 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 22:10 [PATCH 1/2] dt-bindings: mfd: ab8500: Document AB8505 bindings Stephan Gerhold
2019-11-17 22:10 ` Stephan Gerhold
2019-11-17 22:10 ` [PATCH 2/2] mfd: ab8500-core: Add device tree support for AB8505 Stephan Gerhold
2019-11-17 22:10 ` Stephan Gerhold
2019-11-20 20:17 ` Linus Walleij
2019-11-20 20:17 ` Linus Walleij
2019-12-16 10:43 ` Lee Jones
2019-12-16 10:43 ` Lee Jones
2019-11-20 20:16 ` [PATCH 1/2] dt-bindings: mfd: ab8500: Document AB8505 bindings Linus Walleij
2019-11-20 20:16 ` Linus Walleij
2019-12-03 21:40 ` Rob Herring [this message]
2019-12-03 21:40 ` Rob Herring
2019-12-16 10:42 ` Lee Jones
2019-12-16 10:42 ` Lee Jones
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=20191203214019.GA24180@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=stephan@gerhold.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.