linux-kernel - Re: [PATCH] ARC:mm:Fix syntax errors in comments

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: <ac0b07c8-0cd4-6ab4-2939-ead4c813ef78@kernel.org>
Date:   Thu, 23 Jun 2022 18:57:58 -0700
From:   Vineet Gupta <vgupta@...nel.org>
To:     Bagas Sanjaya <bagasdotme@...il.com>,
        Vineet Gupta <vgupta@...nel.org>,
        Jilin Yuan <yuanjilin@...rlc.com>
Cc:     Julia.Lawall@...ia.fr, rdunlap@...radead.org,
        linux-snps-arc@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARC:mm:Fix syntax errors in comments

On 6/23/22 00:56, Bagas Sanjaya wrote:
>> In an ideal world yes. But sometimes maintainer complain to break whitespacxe fixes and such into independent fix. Also as someone said later in the thread, for somebody just getting into kernel and figuring out patch submission etc this could be a perfect dry run and helps improve the code anyways.
>>
> Seems like you missed the point that it's OK to have typofixes while
> doing other real changes (like refactoring) in the same patch.

No I did not.

> Quoting from [1]:
>
>> My opinion is that trivial patches like this are fine as a starting
>> point for new contributors, which is why I acked the previous patch from
>> you guys. However, if we start getting two of these every week it just
>> adds more maintenance burden than it's worth.
> I tend to agree with the last sentence of above quote. Let's pretend that
> I'm the tree maintainer. Besides reviewing real change patches, I get
> flooded by these similar minor cleanup patches that I need to review.
> Some (but not all) these patches have issues (say subject or description
> error) that are repeated.

"Repeated" is the key - First time I'd politely tell them to DTRT but 
will just ignore if things continue.

> Lazily speaking, I'd like to privately notice the
> submitter about the situation, and I withhold these for now.

Funny that you say this: ever since this got posted I now see 3 patches 
for typo fixes :-)
But it is something in maintainers purview and for now i'm ok.

Thx,
-Vineet