[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <179d3a2a-a8bf-44be-b601-e9817c203508@kernel.org>
Date: Thu, 8 May 2025 14:54:34 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Johan Hovold <johan@...nel.org>, srinivas.kandagatla@...aro.org,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: peda@...ntia.se, broonie@...nel.org, andersson@...nel.org,
krzk+dt@...nel.org, ivprusov@...utedevices.com, luca.ceresoli@...tlin.com,
zhoubinbin@...ngson.cn, paulha@...nsource.cirrus.com, lgirdwood@...il.com,
robh@...nel.org, conor+dt@...nel.org, konradybcio@...nel.org,
perex@...ex.cz, tiwai@...e.com, dmitry.baryshkov@....qualcomm.com,
linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
johan+linaro@...nel.org, Christopher Obbard <christopher.obbard@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v6 2/6] mux: gpio: add optional regulator support
On 08/05/2025 14:45, Johan Hovold wrote:
>> nit: "failed to get/enable mux supply" may be more consistent with the
>> other (non-capitalised error) messages and avoids repeating "gpio mux"
>> which will be added by driver core.
>>
>>> +
>>> ret = devm_mux_chip_register(dev, mux_chip);
>>> if (ret < 0)
>>> return ret;
>>
>> Either way:
>>
>> Reviewed-by: Johan Hovold <johan+linaro@...nel.org>
>> Tested-by: Johan Hovold <johan+linaro@...nel.org>
>
> Can someone please pick this one and the binding update up for 6.16?
>
> I see you recently volunteered to do so, Krzysztof? [1]
Sure, thanks for ping. I'll take with your change in err msg.
>
> Johan
>
> [1] https://lore.kernel.org/all/20250501175303.144102-2-krzysztof.kozlowski@linaro.org/
Best regards,
Krzysztof
Powered by blists - more mailing lists