* Re: drm-rust: change branches merged into linux-next [not found] ` <afCi7hSqv6AeGfeo@orome> @ 2026-05-06 23:24 ` Danilo Krummrich 2026-05-07 7:55 ` Thierry Reding 0 siblings, 1 reply; 4+ messages in thread From: Danilo Krummrich @ 2026-05-06 23:24 UTC (permalink / raw) To: Thierry Reding; +Cc: Mark Brown, Alice Ryhl, Thierry Reding, linux-next 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". Thanks, Danilo ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: drm-rust: change branches merged into linux-next 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 2026-05-08 18:52 ` Danilo Krummrich 0 siblings, 2 replies; 4+ messages in thread From: Thierry Reding @ 2026-05-07 7:55 UTC (permalink / raw) To: Danilo Krummrich; +Cc: Thierry Reding, Mark Brown, Alice Ryhl, linux-next [-- Attachment #1: Type: text/plain, Size: 1953 bytes --] 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. Thanks for letting me know, Thierry [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: drm-rust: change branches merged into linux-next 2026-05-07 7:55 ` Thierry Reding @ 2026-05-07 11:47 ` Thierry Reding 2026-05-08 18:52 ` Danilo Krummrich 1 sibling, 0 replies; 4+ messages in thread From: Thierry Reding @ 2026-05-07 11:47 UTC (permalink / raw) To: Danilo Krummrich; +Cc: Thierry Reding, Mark Brown, Alice Ryhl, linux-next [-- 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 --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: drm-rust: change branches merged into linux-next 2026-05-07 7:55 ` Thierry Reding 2026-05-07 11:47 ` Thierry Reding @ 2026-05-08 18:52 ` Danilo Krummrich 1 sibling, 0 replies; 4+ messages in thread From: Danilo Krummrich @ 2026-05-08 18:52 UTC (permalink / raw) To: Thierry Reding; +Cc: Thierry Reding, Mark Brown, Alice Ryhl, linux-next On Thu May 7, 2026 at 9:55 AM CEST, Thierry Reding wrote: > Should be fixed in today's -next. Yes, looks good now, thanks! - Danilo ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-05-08 18:52 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
2026-05-08 18:52 ` Danilo Krummrich
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox