Linux-Next discussions
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Mark Brown <broonie@kernel.org>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Alexander Potapenko <glider@google.com>,
	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
Subject: Re: Policy regarding linux-next only changes
Date: Sun, 26 Jul 2026 23:56:28 -0400	[thread overview]
Message-ID: <ambVmT31R5e8c5g4@mit.edu> (raw)
In-Reply-To: <0e5ea495-07a2-4f83-8fd7-c90563bc12c4@sirena.org.uk>

On Sun, Jul 26, 2026 at 06:49:44PM -0500, Mark Brown wrote:
> The other side of this is that the reason people are noticing that you
> have added these patches is that you are causing breakage and disruption
> for them that catches them by surprise, a lot of what's coming through
> here is that you need to work actively with other people.

I will note that the last person who attempted to push changes to
other subsystems via their own tree was Kent Overstreet.  That was
considered **extremely** anti-social, and after people complained
Linus agreed to reject any pull request that had changes outside of
bcachefs.

This is slightly different, in that it is pushing broken patches into
linux-next, instead of Linus's tree, but I think there is a similar
precedent.  If someone is doing something abusive, it doesn't matter
whether it's because they think they are doing something where the
means justify the ends (whether it's "I fix syzbot bugs" or "I make a
file system which doesn't eat your data").  If you do things in an
antisocial way, Maintainers are *not* obligated to work with you, and
while you can appeal to Linus, you might not like the resolution....

      	      	     	       	   	 - Ted


  reply	other threads:[~2026-07-27  3:58 UTC|newest]

Thread overview: 42+ 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
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 [this message]
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-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=ambVmT31R5e8c5g4@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