linux-kernel - Re: [PATCH 0/2] Minor grammatical fixup for livepatch docs

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: <87h6l4ksni.fsf@meer.lwn.net>
Date:   Wed, 29 Nov 2023 17:10:25 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Bagas Sanjaya <bagasdotme@...il.com>,
        Joe Lawrence <joe.lawrence@...hat.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Documentation <linux-doc@...r.kernel.org>,
        Linux Kernel Livepatching <live-patching@...r.kernel.org>
Cc:     Josh Poimboeuf <jpoimboe@...nel.org>,
        Jiri Kosina <jikos@...nel.org>,
        Miroslav Benes <mbenes@...e.cz>,
        Petr Mladek <pmladek@...e.com>,
        Attreyee Mukherjee <tintinm2017@...il.com>
Subject: Re: [PATCH 0/2] Minor grammatical fixup for livepatch docs

Bagas Sanjaya <bagasdotme@...il.com> writes:

> On 11/29/23 20:53, Joe Lawrence wrote:
>> On 11/29/23 08:25, Bagas Sanjaya wrote:
>>> I was prompted to write this little grammar fix series when reading
>>> the fix from Attreyee [1], with review comments requesting changes
>>> to that fix. So here's my version of the fix, with reviews from [1]
>>> addressed (and distinct grammar fixes splitted).
>>>
>> 
>> Typical kernel workflow would be for Attreyee to incorporate feedback
>> and post their v2 after a day or two.  From the format they posted, it
>> appears to be a first(ish) kernel contribution post.  Let's be kind and
>> patient so they we all may benefit from the practice of iterating on
>> their patch.
>> 
>
> I do this posting because I thought the OP (Attreyee) didn't respond in
> timely manner (just like random Chinese contributors like @cdjrlc.com
> and @208suo.com people).

Seriously?  The original post was on Monday, yours came less than 48
hours later.  Not only can we not expect that kind of rapid turnaround
from anybody, but we actively discourage rapid resending of patches.
Rather than dig yourself in deeper, I suggest you simply apologize to
the original poster and find something more useful to do.

Thanks,

jon