From: Thierry Reding <thierry.reding@gmail.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: Thierry Reding <thierry.reding@kernel.org>,
Mark Brown <broonie@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
linux-next@vger.kernel.org
Subject: Re: drm-rust: change branches merged into linux-next
Date: Thu, 7 May 2026 13:47:16 +0200 [thread overview]
Message-ID: <afx7VUl1PiIWTUvP@orome> (raw)
In-Reply-To: <afxEshceOZza_ulp@orome>
[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]
On Thu, May 07, 2026 at 09:55:09AM +0200, Thierry Reding wrote:
> On Thu, May 07, 2026 at 01:24:38AM +0200, Danilo Krummrich wrote:
> > On Tue Apr 28, 2026 at 2:08 PM CEST, Thierry Reding wrote:
> > >> On Sun, Apr 26, 2026 at 10:52:36PM +0200, Danilo Krummrich wrote:
> > >> >
> > >> > drm-rust https://gitlab.freedesktop.org/drm/rust/kernel.git#drm-rust-next
> > >> > drm-rust-fixes https://gitlab.freedesktop.org/drm/rust/kernel.git#drm-rust-fixes
> > >> >
> > >> > to
> > >> >
> > >> > drm-rust https://gitlab.freedesktop.org/drm/rust/kernel.git#for-linux-next
> > >> > drm-rust-fixes https://gitlab.freedesktop.org/drm/rust/kernel.git#for-linux-next-fixes
> > >
> > > Sorry, I noticed this too late. I've updated these now, so they should
> > > be pulled for tomorrow's -next. I'm about to finish things up for today,
> > > so it'll have the old trees still.
> >
> > Checking today's linux-next tree, it still seems to pull in the "old" branches.
> > This by itself is not a problem; until -rc6 they are exactly the same.
> >
> > However, I noticed that it seems that linux-next stopped fetching new updates
> > from the drm-rust remote.
> >
> > The current head of drm-rust-fixes should be at
> > 0a69ac25bd596d50823d530d0a2004336668c0df, and drm-rust-next should be at
> > 37f748ed0c19e007e7c5677f5d605d6b93841792 (same goes for the new branches).
> >
> > However, today's linux-next release still shows:
> >
> > $ cat Next/SHA1s | grep drm-rust
> > drm-rust-fixes 15e8bae5d930c91b8739a87d75db0a6efca3cb32
> > drm-rust d9a6809478f9815b6455a327aa001737ac7b2c09
> >
> > d9a6809478f9815b6455a327aa001737ac7b2c09 has "CommitDate: Mon Apr 27 18:43:05
> > 2026"; the next commit in my history has "CommitDate: Wed Apr 29 00:57:54 2026
> > +0200".
>
> Sorry, looks like a rookie mistake on my side. The scripts were fetching
> the correct branches but merging the old ones. I should've realized that
> I need to update both the git config *and* the control file.
>
> Should be fixed in today's -next.
Looking good:
$ grep drm-rust Next/SHA1s
drm-rust-fixes 0a69ac25bd596d50823d530d0a2004336668c0df
drm-rust 37f748ed0c19e007e7c5677f5d605d6b93841792
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-07 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DI3DUMHIM5CI.2FMKD5MSWVCAU@kernel.org>
[not found] ` <ae6GpnWSb4Mcel_Q@sirena.co.uk>
[not found] ` <afCi7hSqv6AeGfeo@orome>
2026-05-06 23:24 ` drm-rust: change branches merged into linux-next Danilo Krummrich
2026-05-07 7:55 ` Thierry Reding
2026-05-07 11:47 ` Thierry Reding [this message]
2026-05-08 18:52 ` Danilo Krummrich
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=afx7VUl1PiIWTUvP@orome \
--to=thierry.reding@gmail.com \
--cc=aliceryhl@google.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thierry.reding@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 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.