linux-kernel - Re: [PATCH] Documentation/submitting-patches: Document RESEND tag on patches

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 for Android: free password hash cracker in your pocket

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

Message-ID: <YLa2oDQHqiQr9XhJ@zn.tnic>
Date:   Wed, 2 Jun 2021 00:37:20 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Jonathan Corbet <corbet@....net>
Cc:     x86-ml <x86@...nel.org>, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Documentation/submitting-patches: Document RESEND tag on
 patches

On Tue, Jun 01, 2021 at 04:27:13PM -0600, Jonathan Corbet wrote:
> Oops...somehow I missed the fact that there was something there for me
> to look at and respond to, sorry.

No worries, thanks for taking the time!

> I've just read it through...  if it were me, I would find a way to
> reduce its bulk in the hope that people would actually read it; much of
> what's there is in coding-style.rst (or should be). 

Right, the idea is to point to sections in it during review where the
topic in question is dealt with a greater detail so that we don't have
to type it each time.

I'll take a look at coding-style.rst and see if I can cross-link
sections so that there's no repetition.

> But it's not me, and if you want to keep it I won't whine (much).
> Except about reverse fir tree, perhaps, but nobody listens to me on
> that...:)

Yeah, that is the only correct way! :-)

> I'd say package it up as a maintainer-guide entry and go for it.

Thanks, will do so!

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette