linux-kernel - Re: [PATCH] treewide: Fix common grammar mistake "the the"

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] [day] [month] [year] [list]

Date: Fri, 12 Apr 2024 09:41:10 +0300
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Thorsten Blum <thorsten.blum@...lux.com>, Dan Carpenter
 <dan.carpenter@...aro.org>
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-trace-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-s390@...r.kernel.org,
 speakup@...ux-speakup.org, intel-gfx@...ts.freedesktop.org,
 intel-xe@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
 linux-wireless@...r.kernel.org, linux-scsi@...r.kernel.org,
 linux-afs@...ts.infradead.org, ecryptfs@...r.kernel.org,
 netfs@...ts.linux.dev, linux-fsdevel@...r.kernel.org,
 linux-unionfs@...r.kernel.org, linux-arch@...r.kernel.org,
 io-uring@...r.kernel.org, cocci@...ia.fr, linux-perf-users@...r.kernel.org
Subject: Re: [PATCH] treewide: Fix common grammar mistake "the the"

On Fri, 12 Apr 2024, Thorsten Blum <thorsten.blum@...lux.com> wrote:
> On 11. Apr 2024, at 17:25, Dan Carpenter <dan.carpenter@...aro.org> wrote:
>> 
>> It's tricky to know which tree a patch like this would go through.
>
> The patch is based on the mainline tree. Should I have sent it directly to
> Linus then?
>
> I'm relatively new here and therefore only sent it to the corresponding mailing
> lists.

It's not just about mailing lists, it's also about changes flowing in to
mainline via a plethora of subsystem and driver repos and branches. See
MAINTAINERS. Or this old LWN page [1]. The development happens in those
branches, and if you make treewide changes like this, it's not clear who
should take it, and you also risk unnecessary conflicts if those places
get modified in the individual branches. So it might just be easiest to
split this up to smaller patches sent to the appropriate lists.

Anyway, all that said,

Acked-by: Jani Nikula <jani.nikula@...el.com>

on the i915 changes here.


BR,
Jani.


[1] https://lwn.net/Articles/737094/

-- 
Jani Nikula, Intel