From: Roman Scherer <roman@burningswell.com>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 68257@debbugs.gnu.org
Subject: [bug#68257] [PATCH] gnu: mesa: Build asahi driver on aarch64.
Date: Tue, 16 Jan 2024 17:14:02 +0100 [thread overview]
Message-ID: <CAEc_D2-idC5a+Hp=ktpZmY6V=c92pMFOqLmipDXf55Fnc=56MQ@mail.gmail.com> (raw)
In-Reply-To: <8734uydps7.fsf@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
Hi John,
thanks for your messages. Yes, let's see what happens with this patch in
the core-updates branch.
You are right, that it is a bit unrelated. I was only thinking about the
large rebuild that is probably happening because of jemalloc, not that that
branch got a new purpose.
If it does not get merged with it, I would appreciate the patch being
included in the next mesa-updates round.
Roman
On Tue, Jan 16, 2024 at 2:35 AM John Kehayias <john.kehayias@protonmail.com>
wrote:
> Hello Roman,
>
> On Wed, Jan 10, 2024 at 02:27 PM, Roman Scherer wrote:
>
> > Hi Mathieu,
> >
> > ok, thank you. If there's anything I can do to move this forward, please
> let me know.
> >
>
> I see you just sent a message about applying this on core-updates. I think
> that can be fine since everything is being rebuilt there, if they don't
> mind an unrelated patch. I don't see any issues with adding a driver, but
> I'm not familiar much with aarch64.
>
> As for mesa-updates, I think the next round will be when mesa 24 hits
> stable. They say that should be early February? Anyway, probably about a
> month out. Happy to include this patch there if it doesn't make it for
> core-updates.
>
> John
>
> > Thanks for your help!
> >
> > Roman
> >
> > On Wed, Jan 10, 2024 at 2:23 PM Mathieu Othacehe <othacehe@gnu.org>
> wrote:
> >
> > Hello,
> >
> > > It looks like this issue is now marked as "done" on Debuggs.
> > > How can we proceed with this?
> >
> > I will re-open it as soon as debbugs is back.
> >
> > Mathieu
>
>
[-- Attachment #2: Type: text/html, Size: 2150 bytes --]
next prev parent reply other threads:[~2024-01-16 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 10:53 [bug#68257] [PATCH] gnu: mesa: Build asahi driver on aarch64 Roman Scherer
2024-01-07 20:02 ` bug#68257: " Mathieu Othacehe
2024-01-08 8:54 ` [bug#68257] " Mathieu Othacehe
2024-01-10 9:09 ` Roman Scherer
2024-01-10 13:23 ` Mathieu Othacehe
2024-01-10 13:27 ` Roman Scherer
2024-01-16 1:34 ` John Kehayias via Guix-patches via
2024-01-16 16:14 ` Roman Scherer [this message]
2024-01-24 15:19 ` bug#68257: " Maxim Cournoyer
2024-01-24 15:28 ` [bug#68257] " Roman Scherer
2024-01-24 19:19 ` Maxim Cournoyer
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='CAEc_D2-idC5a+Hp=ktpZmY6V=c92pMFOqLmipDXf55Fnc=56MQ@mail.gmail.com' \
--to=roman@burningswell.com \
--cc=68257@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=othacehe@gnu.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.
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.