linux-kernel - Re: [PATCH v2 1/6] dt-bindings: pinctrl: qcom: correct gpio-ranges in examples for qcs615

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <236fcae1-0632-4691-861a-51a5aeff2ea3@quicinc.com>
Date: Thu, 19 Dec 2024 17:30:31 +0800
From: Lijuan Gao <quic_lijuang@...cinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Bjorn Andersson
	<andersson@...nel.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        Rob Herring
	<robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
	<conor+dt@...nel.org>,
        Jingyi Wang <quic_jingyw@...cinc.com>,
        Konrad Dybcio
	<konradybcio@...nel.org>
CC: <kernel@...cinc.com>, <linux-arm-msm@...r.kernel.org>,
        <linux-gpio@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/6] dt-bindings: pinctrl: qcom: correct gpio-ranges in
 examples for qcs615



在 12/19/2024 4:15 PM, Krzysztof Kozlowski 写道:
> On 19/12/2024 08:59, Lijuan Gao wrote:
>> Correct the gpio-ranges in the QCS615 TLMM pin controller example to
>> include the UFS_RESET pin, which is expected to be wired to the reset
>> pin of the primary UFS memory. This allows the UFS driver to toggle it.
>>
>> Fixes: 55c487ea6084 ("dt-bindings: pinctrl: document the QCS615 Top Level Mode Multiplexer")
>> Signed-off-by: Lijuan Gao <quic_lijuang@...cinc.com>
>> ---
> 
> <form letter>
> This is a friendly reminder during the review process.
> 
> It looks like you received a tag and forgot to add it.
> 
> If you do not know the process, here is a short explanation:
> Please add Acked-by/Reviewed-by/Tested-by tags when posting new
> versions, under or above your Signed-off-by tag. Tag is "received", when
> provided in a message replied to you on the mailing list. Tools like b4
> can help here. However, there's no need to repost patches *only* to add
> the tags. The upstream maintainer will do that for tags received on the
> version they apply.
> 
> https://elixir.bootlin.com/linux/v6.5-rc3/source/Documentation/process/submitting-patches.rst#L577
> 
> If a tag was not added on purpose, please state why and what changed.
> </form letter>
Sorry, my mistake. I didn't realize that Rob Herring had already given 
me an "Acked-by." I updated the commit message in this patch.
> 
> Best regards,
> Krzysztof

-- 
Thx and BRs
Lijuan Gao