From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thorsten Blum <thorsten.blum@toblux.com>,
Dan Carpenter <dan.carpenter@linaro.org>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-s390@vger.kernel.org,
speakup@linux-speakup.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-wireless@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-afs@lists.infradead.org, ecryptfs@vger.kernel.org,
netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-unionfs@vger.kernel.org, linux-arch@vger.kernel.org,
io-uring@vger.kernel.org, cocci@inria.fr,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] treewide: Fix common grammar mistake "the the"
Date: Fri, 12 Apr 2024 09:41:10 +0300 [thread overview]
Message-ID: <87y19j3wxl.fsf@intel.com> (raw)
In-Reply-To: <193B959E-60A3-499A-BFF3-EA7B2D0B6C12@toblux.com>
On Fri, 12 Apr 2024, Thorsten Blum <thorsten.blum@toblux.com> wrote:
> On 11. Apr 2024, at 17:25, Dan Carpenter <dan.carpenter@linaro.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@intel.com>
on the i915 changes here.
BR,
Jani.
[1] https://lwn.net/Articles/737094/
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-04-12 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 15:04 [PATCH] treewide: Fix common grammar mistake "the the" Thorsten Blum
2024-04-11 15:13 ` Randy Dunlap
2024-04-11 15:25 ` Dan Carpenter
2024-04-11 22:39 ` Thorsten Blum
2024-04-12 6:41 ` Jani Nikula [this message]
2024-04-11 15:37 ` Johannes Berg
2024-04-11 16:29 ` Tyler Hicks
2024-04-11 16:45 ` Robin Murphy
2024-04-11 17:11 ` [PATCH v2] " Thorsten Blum
2024-04-11 20:23 ` Christophe JAILLET
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y19j3wxl.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=cocci@inria.fr \
--cc=dan.carpenter@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ecryptfs@vger.kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=io-uring@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=speakup@linux-speakup.org \
--cc=thorsten.blum@toblux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).