From: Dan Carpenter <error27@gmail.com>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: Greg KH <greg@kroah.com>, Theodore Tso <tytso@mit.edu>,
Jonathan Corbet <corbet@lwn.net>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Coping with the new-developer flood
Date: Thu, 6 Aug 2026 22:32:40 +0300 [thread overview]
Message-ID: <anThWLhqipEM34kg@stanley.mountain> (raw)
In-Reply-To: <20260806-industrious-whippet-of-jest-a91eaa@meerkat>
On Thu, Aug 06, 2026 at 01:28:25PM -0400, Konstantin Ryabitsev wrote:
> - actually applies
> - isn't against a known LTS branch
No one wants patches against an LTS branch. That would violate the
stable rules since everything should be upstream first.
Most subsystems take patches against -next and backport the Fixes.
A couple have a tree for the -rc branch and want patches that apply
specifically to that. These are net, bpf and certain Intel networking
drivers. These three subsystems want people to put in the subject
which tree they are working against like [PATCH net-next]"
Everyone else pretty much accepts patches against linux-next. In staging
we tell people to work against staging-next but working against linux-next
is fine. It's basically the same thing.
regards,
dan carpenter
next prev parent reply other threads:[~2026-08-06 19:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 23:26 [MAINTAINERS SUMMIT] Coping with the new-developer flood Jonathan Corbet
2026-08-06 9:24 ` Matthieu Baerts
2026-08-06 10:10 ` Dan Carpenter
2026-08-06 15:42 ` Theodore Tso
2026-08-06 15:57 ` Greg KH
2026-08-06 17:28 ` Konstantin Ryabitsev
2026-08-06 18:56 ` Shuah Khan
2026-08-06 19:32 ` Dan Carpenter [this message]
2026-08-06 21:14 ` Mark Brown
2026-08-07 3:23 ` Theodore Tso
2026-08-07 9:20 ` Matthieu Baerts
2026-08-07 11:56 ` Laurent Pinchart
2026-08-07 12:28 ` James Bottomley
2026-08-07 12:40 ` Laurent Pinchart
2026-08-07 12:47 ` Arnaldo Carvalho de Melo
2026-08-07 13:36 ` Laurent Pinchart
2026-08-07 13:56 ` Rafael J. Wysocki (Intel)
2026-08-07 16:38 ` Miguel Ojeda
2026-08-07 12:51 ` James Bottomley
2026-08-07 13:34 ` Laurent Pinchart
2026-08-07 13:42 ` Mark Brown
2026-08-07 13:02 ` Mimi Zohar
2026-08-07 13:12 ` Dan Carpenter
2026-08-07 16:37 ` Miguel Ojeda
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=anThWLhqipEM34kg@stanley.mountain \
--to=error27@gmail.com \
--cc=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=ksummit@lists.linux.dev \
--cc=mricon@kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.