linux-kernel - Re: [PATCH] riscv: dts: starfive: Fix a typo in StarFive JH7110 pin function definitions

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: <e4e19875-c02c-4673-814b-86090223b55d@freeshell.de>
Date: Fri, 13 Dec 2024 11:58:29 -0800
From: E Shattow <e@...eshell.de>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Emil Renner Berthing <kernel@...il.dk>, Conor Dooley <conor@...nel.org>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt
 <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
 Hal Feng <hal.feng@...rfivetech.com>,
 Jianlong Huang <jianlong.huang@...rfivetech.com>,
 Conor Dooley <conor.dooley@...rochip.com>, linux-riscv@...ts.infradead.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] riscv: dts: starfive: Fix a typo in StarFive JH7110 pin
 function definitions

Hi Krzysztof,

On 12/13/24 01:37, Krzysztof Kozlowski wrote:
> On Mon, Dec 09, 2024 at 08:19:56PM -0800, E Shattow wrote:
>> Fix a typo in StarFive JH7110 pin function definitions for GPOUT_SYS_SDIO1_DATA4
>>
>> Fixes: e22f09e598d12 ("riscv: dts: starfive: Add StarFive JH7110 pin function definitions")
>> Signed-off-by: E Shattow <e@...eshell.de>
>> Acked-by: Hal Feng <hal.feng@...rfivetech.com>
>> ---
> 
> Why are you sending the same multiple times? Where is the changelog and
> proper patch versioning?
> 
> Best regards,
> Krzysztof
> 

I did respond to Hal's comment that the patch is missing a commit title 
description and that I would re-send. How instead should the message be 
formatted so the patch commit title description is changed but the patch 
is not the same being sent multiple times?  And now, again, based on 
your comment that this is not a typo I will again change the commit 
description but I don't know how to do that without sending again as a 
duplicate.

Thank you for the review and for your patience with me when I am 
learning how to participate.

-E