[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1fac581e-ef02-4576-0dbf-67662a29f724@collabora.com>
Date: Wed, 16 Nov 2022 09:50:37 +0100
From: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
agross@...nel.org
Cc: andersson@...nel.org, konrad.dybcio@...aro.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, jassisinghbrar@...il.com,
srinivas.kandagatla@...aro.org, jic23@...nel.org, lars@...afoo.de,
keescook@...omium.org, tony.luck@...el.com, gpiccoli@...lia.com,
evgreen@...omium.org, gregkh@...uxfoundation.org,
a39.skl@...il.com, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-iio@...r.kernel.org, linux-hardening@...r.kernel.org,
marijn.suijten@...ainline.org, kernel@...labora.com, luca@...tu.xyz
Subject: Re: [PATCH v2 02/11] dt-bindings: nvmem: Fix qcom,qfprom compatibles
enum ordering
Il 15/11/22 17:42, Krzysztof Kozlowski ha scritto:
> On 11/11/2022 13:01, AngeloGioacchino Del Regno wrote:
>> Move qcom,msm8974-qfprom after qcom,msm8916-qfprom to respect
>> alphabetical ordering.
>>
>> Fixes: c8b336bb1aeb ("dt-bindings: nvmem: Add soc qfprom compatible strings")
>
> It's a style, code readability, but not a bug. I propose to drop the tag.
>
> With that:
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>
>
Should I send a v3, or is it possible to drop the tag while applying it?
Thanks,
Angelo
Powered by blists - more mailing lists