From: Jani Nikula <jani.nikula@intel.com>
To: dim-tools@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org, airlied@gmail.com,
daniel@ffwll.ch
Subject: [Intel-gfx] [drm-rerere] nightly.conf: drop sound tree from drm-tip altogether
Date: Thu, 6 Jul 2023 12:28:50 +0300 [thread overview]
Message-ID: <20230706092850.3417782-1-jani.nikula@intel.com> (raw)
We used to have the sound branches be part of drm-tip to help
development of DP and HDMI audio. However, we always used to run into
problems with the sound branches merging Linus' master at non-tagged
random commits, wreaking havoc especially during the merge windows. We
only ever want to have tagged stuff merged back from Linus' tree to
drm-tip.
We introduced a mechanism in dim to hold back branches at certain
commits, just to hold back sound branches when problems arise. We moved
it along, but in the end nobody has updated this in literally years, and
sound branches have been held back at v5.13.
The merge window is currently open, and AFAICT the sound/for-linus
branch again contains commits from the merge window.
Let's just forget about the sound tree, as nobody has really missed it
since v5.13, and focus on the drm branches.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
nightly.conf | 7 -------
1 file changed, 7 deletions(-)
diff --git a/nightly.conf b/nightly.conf
index 73aec820e98f..c1e22800e276 100644
--- a/nightly.conf
+++ b/nightly.conf
@@ -46,11 +46,6 @@ git://anongit.freedesktop.org/drm/drm
https://anongit.freedesktop.org/git/drm/drm
https://anongit.freedesktop.org/git/drm/drm.git
"
-drm_tip_repos[sound-upstream]="
-git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
-https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
-https://kernel.googlesource.com/pub/scm/linux/kernel/git/tiwai/sound.git
-"
drm_tip_repos[linux-upstream]="
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
@@ -79,8 +74,6 @@ drm_tip_config=(
"drm-intel drm-intel-next"
"drm-intel drm-intel-gt-next"
- "sound-upstream for-linus v5.13"
- "sound-upstream for-next v5.13"
"drm-intel topic/core-for-CI"
"drm-misc topic/i915-ttm"
"drm topic/nouveau-misc"
--
2.39.2
next reply other threads:[~2023-07-06 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 9:28 Jani Nikula [this message]
2023-07-06 14:00 ` [Intel-gfx] [drm-rerere] nightly.conf: drop sound tree from drm-tip altogether Alex Deucher
2023-07-06 14:14 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2023-07-11 15:40 ` [Intel-gfx] [drm-rerere] " Maarten Lankhorst
2023-07-11 15:48 ` Jani Nikula
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=20230706092850.3417782-1-jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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