From: Jonathan Cameron <jic23@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Cc: Fabrice Gasnier <fabrice.gasnier@st.com>,
Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Benjamin GAIGNARD <benjamin.gaignard@st.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] dt-bindings: iio: update STM32 timers clock names
Date: Sun, 11 Jun 2017 12:20:09 +0100 [thread overview]
Message-ID: <20170611122009.37ed409b@kernel.org> (raw)
In-Reply-To: <CA+M3ks4z46rPmjBt=pfJQBBjr5Hr7Oj4P=tv5wjo9WB_Ca_vsA@mail.gmail.com>
On Fri, 9 Jun 2017 09:43:42 +0200
Benjamin Gaignard <benjamin.gaignard@linaro.org> wrote:
> 2017-06-09 9:37 GMT+02:00 Fabrice Gasnier <fabrice.gasnier@st.com>:
> > Clock name has been updated during driver/DT binding review:
> > https://lkml.org/lkml/2016/12/13/718
> > Update DT binding doc to reflect this.
> >
> > Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
Same fixes tag as previous as this is an example of the binding for the
mfd rather than actually part of the IIO binding.
Fixes: d0f949e220fd ("mfd: Add STM32 Timers driver")
Acked-by: Jonathan Cameron <jic23@kernel.org>
I'm assuming Rob / Mark or Lee will pick this up. If people
do want it to go through the IIO tree let me know.
Jonathan
> > ---
> > Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt b/Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt
> > index 55a653d..6abc755 100644
> > --- a/Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt
> > +++ b/Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt
> > @@ -14,7 +14,7 @@ Example:
> > compatible = "st,stm32-timers";
> > reg = <0x40010000 0x400>;
> > clocks = <&rcc 0 160>;
> > - clock-names = "clk_int";
> > + clock-names = "int";
> >
> > timer@0 {
> > compatible = "st,stm32-timer-trigger";
> > --
> > 1.9.1
> >
> Acked-by: Benjamin Gaignard <benjamin.gaignard@linaro.org>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-11 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 7:37 [PATCH 0/2] Fix STM32 timers dt-bindings Fabrice Gasnier
2017-06-09 7:37 ` [PATCH 1/2] dt-bindings: mfd: update STM32 timers clock names Fabrice Gasnier
2017-06-09 7:43 ` Benjamin Gaignard
2017-06-11 11:15 ` Jonathan Cameron
2017-06-09 7:37 ` [PATCH 2/2] dt-bindings: iio: " Fabrice Gasnier
2017-06-09 7:43 ` Benjamin Gaignard
2017-06-11 11:20 ` Jonathan Cameron [this message]
2017-06-14 15:16 ` Fabrice Gasnier
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=20170611122009.37ed409b@kernel.org \
--to=jic23@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@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).