linux-kernel - Re: [PATCH v2] docs: Fix typo in comment

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: <6ca59494-cc64-d85c-98e8-e9bef2a04c15@infradead.org>
Date:   Thu, 21 Jul 2022 11:40:06 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Jonathan Corbet <corbet@....net>, Slark Xiao <slark_xiao@....com>,
        kafai <kafai@...com>
Cc:     Baoquan He <bhe@...hat.com>, vgoyal <vgoyal@...hat.com>,
        dyoung <dyoung@...hat.com>, ast <ast@...nel.org>,
        daniel <daniel@...earbox.net>, andrii <andrii@...nel.org>,
        "martin.lau" <martin.lau@...ux.dev>, song <song@...nel.org>,
        yhs <yhs@...com>, "john.fastabend" <john.fastabend@...il.com>,
        kpsingh <kpsingh@...nel.org>, sdf <sdf@...gle.com>,
        haoluo <haoluo@...gle.com>, jolsa <jolsa@...nel.org>,
        "william.gray" <william.gray@...aro.org>,
        dhowells <dhowells@...hat.com>, peterz <peterz@...radead.org>,
        mingo <mingo@...hat.com>, will <will@...nel.org>,
        longman <longman@...hat.com>,
        "boqun.feng" <boqun.feng@...il.com>, tglx <tglx@...utronix.de>,
        bigeasy <bigeasy@...utronix.de>,
        kexec <kexec@...ts.infradead.org>,
        linux-doc <linux-doc@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        bpf <bpf@...r.kernel.org>,
        linux-cachefs <linux-cachefs@...hat.com>
Subject: Re: [PATCH v2] docs: Fix typo in comment



On 7/21/22 11:36, Jonathan Corbet wrote:
> "Slark Xiao" <slark_xiao@....com> writes:
> 
>> May I know the maintainer of one subsystem could merge the changes
>> contains lots of subsystem?  I also know this could be filtered by
>> grep and sed command, but that patch would have dozens of maintainers
>> and reviewers.
> 
> Certainly I don't think I can merge a patch touching 166 files across
> the tree.  This will need to be broken down by subsystem, and you may
> well find that there are some maintainers who don't want to deal with
> this type of minor fix.

We have also seen cases where "the the" should be replaced by "then the"
or some other pair of words, so some of these changes could fall into
that category.

-- 
~Randy