From: Rob Herring <robh@kernel.org>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>,
linux-can@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: phy: ti, tcan104x-can: Document mux-states property
Date: Tue, 8 Mar 2022 10:39:55 -0600 [thread overview]
Message-ID: <YieG22mgIzsL7TMn@robh.at.kernel.org> (raw)
In-Reply-To: <20211216041012.16892-2-a-govindraju@ti.com>
On Thu, Dec 16, 2021 at 09:40:11AM +0530, Aswath Govindraju wrote:
> On some boards, for routing CAN signals from controller to transceivers,
> muxes might need to be set. This can be implemented using mux-states
> property. Therefore, document the same in the respective bindings.
>
> Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
> ---
> Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
As the warning without this is still there and it hasn't been resent,
I've applied it.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>,
linux-can@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: phy: ti, tcan104x-can: Document mux-states property
Date: Tue, 8 Mar 2022 10:39:55 -0600 [thread overview]
Message-ID: <YieG22mgIzsL7TMn@robh.at.kernel.org> (raw)
In-Reply-To: <20211216041012.16892-2-a-govindraju@ti.com>
On Thu, Dec 16, 2021 at 09:40:11AM +0530, Aswath Govindraju wrote:
> On some boards, for routing CAN signals from controller to transceivers,
> muxes might need to be set. This can be implemented using mux-states
> property. Therefore, document the same in the respective bindings.
>
> Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
> ---
> Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
As the warning without this is still there and it hasn't been resent,
I've applied it.
Rob
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-03-08 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 4:10 [PATCH v3 0/2] CAN: Add support for setting mux Aswath Govindraju
2021-12-16 4:10 ` Aswath Govindraju
2021-12-16 4:10 ` [PATCH v3 1/2] dt-bindings: phy: ti,tcan104x-can: Document mux-states property Aswath Govindraju
2021-12-16 4:10 ` [PATCH v3 1/2] dt-bindings: phy: ti, tcan104x-can: " Aswath Govindraju
2021-12-16 20:33 ` [PATCH v3 1/2] dt-bindings: phy: ti,tcan104x-can: " Rob Herring
2021-12-16 20:33 ` Rob Herring
2022-03-08 16:39 ` Rob Herring [this message]
2022-03-08 16:39 ` [PATCH v3 1/2] dt-bindings: phy: ti, tcan104x-can: " Rob Herring
2021-12-16 4:10 ` [PATCH v3 2/2] phy: phy-can-transceiver: Add support for setting mux Aswath Govindraju
2021-12-16 4:10 ` Aswath Govindraju
2021-12-23 11:28 ` [PATCH v3 0/2] CAN: " Vinod Koul
2021-12-23 11:28 ` Vinod Koul
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=YieG22mgIzsL7TMn@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mkl@pengutronix.de \
--cc=vkoul@kernel.org \
--cc=wg@grandegger.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.