[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174437342110.673813.5478003699967879937.b4-ty@kernel.org>
Date: Fri, 11 Apr 2025 17:40:21 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Rob Herring <robh@...nel.org>, Marc Kleine-Budde <mkl@...gutronix.de>,
Vincent Mailhol <mailhol.vincent@...adoo.fr>,
Kishon Vijay Abraham I <kishon@...nel.org>, Peter Rosin <peda@...ntia.se>,
Aswath Govindraju <a-govindraju@...com>,
Biju Das <biju.das.jz@...renesas.com>,
Geert Uytterhoeven <geert+renesas@...der.be>
Cc: linux-can@...r.kernel.org, linux-phy@...ts.infradead.org,
linux-renesas-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] phy: can-transceiver: Re-instate "mux-states"
property presence check
On Thu, 20 Mar 2025 16:15:42 +0100, Geert Uytterhoeven wrote:
> On the Renesas Gray Hawk Single development board:
>
> can-transceiver-phy can-phy0: /can-phy0: failed to get mux-state (0)
>
> "mux-states" is an optional property for CAN transceivers. However,
> mux_get() always prints an error message in case of an error, including
> when the property is not present, confusing the user.
>
> [...]
Applied, thanks!
[1/1] phy: can-transceiver: Re-instate "mux-states" property presence check
commit: e153fdea9db04dd0e2e536e2eb125b16bbbc2af7
Best regards,
--
~Vinod
Powered by blists - more mailing lists