From: "Theodore Tso" <tytso@mit.edu>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Alexander Potapenko <glider@google.com>,
Mark Brown <broonie@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Aleksandr Nogikh <nogikh@google.com>,
Boqun Feng <boqun@kernel.org>, Gary Guo <gary@garyguo.net>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Miguel Ojeda <ojeda@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
peterz@infradead.org, will@kernel.org, longman@redhat.com,
mingo@kernel.org, gregkh@linuxfoundation.org,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Subject: Re: Policy regarding linux-next only changes
Date: Sat, 25 Jul 2026 18:00:13 -0400 [thread overview]
Message-ID: <amUuEfXKXPRP0cGF@mit.edu> (raw)
In-Reply-To: <c0272e64-a849-4fe0-8131-ecf6c724f558@I-love.SAKURA.ne.jp>
On Sat, Jul 25, 2026 at 02:20:29PM -0500, Tetsuo Handa wrote:
> Not all developers have enough money to pay to companies/organizations.
> Some developers (including me) are contributing by spending their time
> instead of paying money.
>
> Your statements sound like "Poor men/women cannot participate into
> the Linux kernel development." Please don't assume that everything
> is controlled by "who pays the money?".
If they want to spend their own personal time, that's fine. I just
don't want companies or hobbists spending *my* personal time.
> Please respond to syzbot-related patches.
Oh, I, or some other ext4 developer do respond --- if it's a bug fix.
I wish more of the contributors would actually pay attention to the
Sashiko reviews, and actually *test* the patches using "kvm-xfstests
smoke" which takes 20 minutes, but we'll respond, one way or another.
We might NACK the patch if it destroys performance because it adds
tests in a hot path and it's addressing a really pointless syzbot scenario
which requires root privilegs to modify the loop device while the file
system is mounted, however.
However, if it's a debugging patch to fix what we might consider a
rather pointless syzbot bug (and there are an awful lot of those, at
least for ext4) it might take a while for me to respond. And if it's
about landing ext4 patches from a non-ext4 tree, abusing the
linux-next tree, that's a somewhat different matter....
- Ted
next prev parent reply other threads:[~2026-07-25 22:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 11:49 Policy regarding linux-next only changes Gary Guo
2026-07-02 12:49 ` Tetsuo Handa
2026-07-02 13:37 ` Miguel Ojeda
2026-07-02 14:11 ` Boqun Feng
2026-07-04 10:14 ` Tetsuo Handa
2026-07-04 12:06 ` Miguel Ojeda
2026-07-04 13:22 ` Theodore Tso
2026-07-05 11:36 ` Tetsuo Handa
2026-07-05 12:02 ` Miguel Ojeda
2026-07-05 12:06 ` Miguel Ojeda
2026-07-05 12:20 ` Mark Brown
2026-07-05 12:06 ` Mark Brown
2026-07-05 14:16 ` Tetsuo Handa
2026-07-06 17:23 ` Mark Brown
2026-07-20 10:06 ` Tetsuo Handa
2026-07-21 9:38 ` Alexander Potapenko
2026-07-21 11:48 ` Tetsuo Handa
2026-07-22 14:19 ` Alexander Potapenko
2026-07-22 15:07 ` Tetsuo Handa
2026-07-22 17:47 ` Theodore Tso
2026-07-24 12:11 ` Tetsuo Handa
2026-07-24 13:50 ` Theodore Tso
2026-07-24 14:35 ` Tetsuo Handa
2026-07-24 14:51 ` Theodore Tso
2026-07-24 15:29 ` Tetsuo Handa
2026-07-24 21:05 ` Theodore Tso
2026-07-25 5:20 ` Tetsuo Handa
2026-07-25 22:00 ` Theodore Tso [this message]
2026-07-24 17:49 ` Miguel Ojeda
2026-07-25 3:44 ` Tetsuo Handa
2026-07-25 9:38 ` Miguel Ojeda
2026-07-25 10:38 ` Tetsuo Handa
2026-07-25 13:27 ` Boqun Feng
2026-07-26 17:49 ` Mark Brown
2026-07-27 3:56 ` Theodore Tso
2026-07-05 9:05 ` [PATCH] lockdep: Enable the printing of held locks of running non-current tasks (was: Policy regarding linux-next only changes) Ingo Molnar
2026-07-05 11:05 ` [PATCH] lockdep: Enable the printing of held locks of running non-current tasks Tetsuo Handa
2026-07-07 7:20 ` [PATCH -v2] lockdep: Enable the printing of held locks of remote running tasks and print task CPU Ingo Molnar
2026-07-07 13:10 ` Tetsuo Handa
2026-07-08 8:37 ` Ingo Molnar
2026-07-07 7:21 ` [tip: locking/debug] " tip-bot2 for Ingo Molnar
2026-07-08 8:41 ` [tip: locking/core] " tip-bot2 for Ingo Molnar
2026-07-05 14:59 ` Policy regarding linux-next only changes Boqun Feng
2026-07-02 13:22 ` Mark Brown
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=amUuEfXKXPRP0cGF@mit.edu \
--to=tytso@mit.edu \
--cc=boqun@kernel.org \
--cc=broonie@kernel.org \
--cc=gary@garyguo.net \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=longman@redhat.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@kernel.org \
--cc=nogikh@google.com \
--cc=ojeda@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
/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