From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: I have merged wip-ppc64le-for-master to master
Date: Tue, 30 Mar 2021 23:18:11 -0700 [thread overview]
Message-ID: <87h7krzw0s.fsf@gmail.com> (raw)
In-Reply-To: <87y2e5gcrn.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 30 Mar 2021 12:24:28 +0200")
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Chris Marusich <cmmarusich@gmail.com> skribis:
>
>> FYI, I have merged wip-ppc64le-for-master to master and closed bug
>> 47182. I have also deleted the wip-ppc64le-for-master branch.
>
> Yay, congrats! \o/
>
> I now have access to the OSUOSL POWER9 machine. I’ve set up offloading
> and it seems to work well.
>
> Thanks to all the hackers involved + OSUOSL!
That's fantastic news! Please let us know if you have any trouble
running the "make release" target. I think the recipe is good to go,
since SUPPORTED_SYSTEMS now contains powerpc64le-linux.
Is there something else I can help with for the release? Leo and I are
working on a blog post; we should probably share it soon for review.
By the way, I have just now updated the documentation in commit
e52ec6c64a17a99ae4bb6ff02309067499915b06 and the news.scm file in
0374617920e3d278e68c71826fec1f590921e31b.
I'm really excited about this release! I'm looking forward to
continuing to work on POWER9 support with everyone going forward.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
prev parent reply other threads:[~2021-03-31 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 6:41 I have merged wip-ppc64le-for-master to master Chris Marusich
2021-03-24 8:54 ` Christopher Baines
2021-03-24 9:29 ` zimoun
2021-03-24 10:25 ` Efraim Flashner
2021-03-24 11:17 ` Léo Le Bouter
2021-03-30 10:24 ` Ludovic Courtès
2021-03-31 6:18 ` Chris Marusich [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7krzw0s.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).