From: "Danilo Krummrich" <dakr@kernel.org>
To: "Jani Nikula" <jani.nikula@linux.intel.com>
Cc: "Dave Airlie" <airlied@gmail.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Alex Deucher" <alexdeucher@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org,
"Mark Brown" <broonie@kernel.org>,
linux-next@vger.kernel.org
Subject: Re: [RFC] linux-next: replace the DRM trees with a single drm-for-linux-next
Date: Fri, 06 Nov 2026 17:37:47 +0100 [thread overview]
Message-ID: <DMO9X7V4K1MQ.2PSHDUJKA9Z2B@kernel.org> (raw)
In-Reply-To: <3678ff00381a70148d6abafcf20ba3726bff2fc7@intel.com>
On Fri Nov 6, 2026 at 12:08 PM CET, Jani Nikula wrote:
> Anyway, how about just *prompting* "Is this expected to be the final
> pull request for the development cycle?", and if yes, update
> drm-*-next-fixes while at it, and have the automation handle the rest.
I think that's a good idea! So what about just git request-pull prompts:
Close this tree for the upcoming merge window?
and in addition have --close-tree / --keep-tree-open options that bypass the
prompt.
next prev parent reply other threads:[~2026-11-06 16:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 18:41 [RFC] linux-next: replace the DRM trees with a single drm-for-linux-next Rodrigo Vivi
2026-11-02 18:51 ` Danilo Krummrich
2026-11-02 19:20 ` Rodrigo Vivi
2026-11-02 20:01 ` Danilo Krummrich
2026-11-03 2:05 ` Dave Airlie
2026-11-03 19:32 ` Danilo Krummrich
2026-11-03 20:33 ` Rodrigo Vivi
2026-11-03 21:04 ` Danilo Krummrich
2026-11-03 21:19 ` Alex Deucher
2026-11-03 22:48 ` Rodrigo Vivi
2026-11-03 23:01 ` Danilo Krummrich
2026-11-04 2:37 ` Rodrigo Vivi
2026-11-04 3:29 ` Dave Airlie
2026-11-04 11:08 ` Danilo Krummrich
2026-11-04 17:44 ` Rodrigo Vivi
2026-11-04 22:35 ` Danilo Krummrich
2026-11-05 21:52 ` Rodrigo Vivi
2026-11-05 23:27 ` Danilo Krummrich
2026-11-05 13:44 ` Jani Nikula
2026-11-05 21:08 ` Danilo Krummrich
2026-11-06 11:08 ` Jani Nikula
2026-11-06 12:10 ` Mark Brown
2026-11-06 16:37 ` Danilo Krummrich [this message]
2026-11-03 22:39 ` Rodrigo Vivi
2026-11-02 18:58 ` Mark Brown
2026-11-02 23:07 ` Alex Deucher
2026-11-03 20:35 ` Rodrigo Vivi
2026-11-03 21:24 ` Alex Deucher
2026-11-04 5:49 ` Thorsten Leemhuis
2026-11-04 11:48 ` Mark Brown
2026-11-04 12:46 ` Sasha Levin
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=DMO9X7V4K1MQ.2PSHDUJKA9Z2B@kernel.org \
--to=dakr@kernel.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=aliceryhl@google.com \
--cc=broonie@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-next@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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