From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: 73288@debbugs.gnu.org
Cc: Efraim Flashner <efraim.flashner@gmail.com>
Subject: [bug#73288] Request for merging "mesa-updates" branch
Date: Mon, 16 Sep 2024 02:38:16 +0000 [thread overview]
Message-ID: <87bk0opbl7.fsf_-_@protonmail.com> (raw)
Hello Guix,
The mesa-updates branch I think is just almost ready for merging. Besides some other fixes and updates, the main series is tracked at <https://issues.guix.gnu.org/73071>. There is an update to add NVK support to mesa for x86_64-linux which I need to review and push (and rebase to get more fixes from master).
Coverage looks good for x86_64 and i686 on QA, with powerpc64le as well on Berlin. I worry that aarch64 and others may have stalled out on Bordeaux. Perhaps Efraim can chime in there.
With an update for NVK for x86_64, that will take maybe a day to catch up again in builds but tends to be pretty quick. I'm not aware of other blockers.
Thanks!
John
next reply other threads:[~2024-09-16 2:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 2:38 John Kehayias via Guix-patches via [this message]
2024-09-23 5:34 ` [bug#73288] Request for merging "mesa-updates" branch Efraim Flashner
2024-09-30 0:11 ` John Kehayias
2024-10-02 20:53 ` Sharlatan Hellseher
2024-10-03 8:56 ` Steve George via Guix-patches
2024-10-04 8:21 ` Ludovic Courtès
2024-10-03 9:01 ` Steve George via Guix-patches
2024-10-19 14:43 ` [bug#73288] Advance in queue Andreas Enge
2024-10-31 19:35 ` [bug#73288] Request for merging "mesa-updates" branch Sharlatan Hellseher
2024-11-03 10:04 ` Z572
2024-11-03 13:02 ` Efraim Flashner
2024-11-04 2:32 ` John Kehayias via Guix-patches via
2024-11-04 16:50 ` Z572
2024-11-05 4:15 ` John Kehayias via Guix-patches via
2024-11-05 10:35 ` Efraim Flashner
2024-11-05 18:49 ` bug#73288: " John Kehayias via Guix-patches via
2024-11-04 9:33 ` [bug#73288] " Christopher Baines
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=87bk0opbl7.fsf_-_@protonmail.com \
--to=guix-patches@gnu.org \
--cc=73288@debbugs.gnu.org \
--cc=efraim.flashner@gmail.com \
--cc=john.kehayias@protonmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.