From: Rob Herring <robh@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Tero Kristo <kristo@kernel.org>,
devicetree@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 2/3] dt-bindings: clock: ti: Add clock-output-names for clockctrl
Date: Fri, 11 Feb 2022 08:11:00 -0600 [thread overview]
Message-ID: <YgZudCnBK64ilTwX@robh.at.kernel.org> (raw)
In-Reply-To: <20220203112337.19821-2-tony@atomide.com>
On Thu, 03 Feb 2022 13:23:36 +0200, Tony Lindgren wrote:
> This allows us to use clock-output-names for the clockctrl instance
> name instead of relying on a custom compatible or non-standard node
> names.
>
> Cc: Stephen Boyd <sboyd@kernel.org>
> Cc: Tero Kristo <kristo@kernel.org>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
> Documentation/devicetree/bindings/clock/ti-clkctrl.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Tero Kristo <kristo@kernel.org>,
devicetree@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 2/3] dt-bindings: clock: ti: Add clock-output-names for clockctrl
Date: Fri, 11 Feb 2022 08:11:00 -0600 [thread overview]
Message-ID: <YgZudCnBK64ilTwX@robh.at.kernel.org> (raw)
In-Reply-To: <20220203112337.19821-2-tony@atomide.com>
On Thu, 03 Feb 2022 13:23:36 +0200, Tony Lindgren wrote:
> This allows us to use clock-output-names for the clockctrl instance
> name instead of relying on a custom compatible or non-standard node
> names.
>
> Cc: Stephen Boyd <sboyd@kernel.org>
> Cc: Tero Kristo <kristo@kernel.org>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
> Documentation/devicetree/bindings/clock/ti-clkctrl.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
Acked-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
next prev parent reply other threads:[~2022-02-11 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 11:23 [PATCH 1/3] dt-bindings: omap: Add clock-output-names and #clock-cells Tony Lindgren
2022-02-03 11:23 ` Tony Lindgren
2022-02-03 11:23 ` [PATCH 2/3] dt-bindings: clock: ti: Add clock-output-names for clockctrl Tony Lindgren
2022-02-03 11:23 ` Tony Lindgren
2022-02-11 14:11 ` Rob Herring [this message]
2022-02-11 14:11 ` Rob Herring
2022-02-03 11:23 ` [PATCH 3/3] dt-bindings: clock: ti: Add clock-output-names for TI composite clocks Tony Lindgren
2022-02-03 11:23 ` Tony Lindgren
2022-02-11 14:11 ` Rob Herring
2022-02-11 14:11 ` Rob Herring
2022-02-11 14:10 ` [PATCH 1/3] dt-bindings: omap: Add clock-output-names and #clock-cells Rob Herring
2022-02-11 14:10 ` Rob Herring
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=YgZudCnBK64ilTwX@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tony@atomide.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 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.