From: Krzysztof Kozlowski <krzk@kernel.org>
To: ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Hidden commits from next (aka why maintainers hoard them in backpack)
Date: Sun, 14 Dec 2025 02:19:16 +0100 [thread overview]
Message-ID: <2f9d40a8-a913-415a-b173-287bf6eb4373@kernel.org> (raw)
In-Reply-To: <299e6601-a83e-4e5d-9dd9-12ae796cd913@kernel.org>
On 11/09/2025 13:04, Krzysztof Kozlowski wrote:
> Hi,
>
>
> I have noticed at least a few cases where sub-maintainers collect
> patches, but their trees are not included linux-next. Or their patches
> are not fed to linux-next.
>
> I don’t see a good reason to keep valid, proper patches - collected by
> trusted sub-maintainers and intended for upstream submission - out of
> linux-next. If a sub-maintainer is trusted in collecting patches and
> sending them to the upstream maintainer, these commits should be visible
> in the linux-next.
>
> I have occasionally asked sub-maintainers to add their trees to the
> linux-next, and sometimes this worked. In other cases it could not work
> for various reasons, e.g. workflow of the upstream maintainer or
> reluctance to share commits early. These reasons are what I would like
> to discuss and, hopefully, improve.
>
>
> Why is that a problem?
> ======================
> Patch was reviewed on the list day X and applied by the sub-maintainer.
https://lwn.net/Articles/1050027/
I am very happy that the topic proposal I submitted in September for
this maintainer's summit got some traction and lead to actual
discussion. Nice to know that this was an useful email/proposal and that
the problem is important enough to discuss it.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-12-14 1:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 11:04 Krzysztof Kozlowski
2025-09-11 11:44 ` Krzysztof Kozlowski
2025-09-11 12:05 ` Mark Brown
2025-09-11 18:45 ` Dan Carpenter
2025-09-11 12:06 ` Jiri Kosina
2025-09-11 12:10 ` Krzysztof Kozlowski
2025-09-11 13:18 ` James Bottomley
2025-09-11 13:49 ` Mark Brown
2025-09-11 15:32 ` James Bottomley
2025-09-11 16:02 ` Mark Brown
2025-09-11 16:11 ` James Bottomley
2025-09-11 16:50 ` Mark Brown
2025-09-11 12:27 ` Laurent Pinchart
2025-09-11 12:31 ` Bartosz Golaszewski
2025-09-11 12:33 ` Laurent Pinchart
2025-09-11 12:42 ` Krzysztof Kozlowski
2025-09-11 12:58 ` Greg KH
2025-09-12 9:03 ` Dan Carpenter
2025-09-11 12:34 ` Geert Uytterhoeven
2025-09-11 12:35 ` Johannes Berg
2025-09-11 12:36 ` Laurent Pinchart
2025-09-11 12:48 ` Mark Brown
2025-09-11 12:47 ` Krzysztof Kozlowski
2025-09-11 12:53 ` Laurent Pinchart
2025-09-11 13:40 ` Mark Brown
2025-09-11 14:25 ` Steven Rostedt
2025-09-11 19:29 ` Laurent Pinchart
2025-09-11 19:43 ` Steven Rostedt
2025-09-12 9:52 ` Vlastimil Babka
2025-09-12 17:45 ` Steven Rostedt
2025-09-11 12:49 ` Sasha Levin
2025-09-12 11:55 ` Krzysztof Kozlowski
2025-12-14 1:19 ` Krzysztof Kozlowski [this message]
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=2f9d40a8-a913-415a-b173-287bf6eb4373@kernel.org \
--to=krzk@kernel.org \
--cc=ksummit@lists.linux.dev \
/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