From: phodina via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 49898@debbugs.gnu.org
Subject: [bug#49898] [PATCH v5] gnu: Add spectre-meltdown-checker.
Date: Sun, 26 Jun 2022 11:07:26 +0000 [thread overview]
Message-ID: <MDXych3ebMv3NuAgJgpGtQ68v2qK_c7YCVZnGR0rVKkymTzHzqZ6um7eS_MVxV3Y862FQ2UVc7D5cQrsCxNkq4eu7tf9iYzcvxnxPPFqNbY=@protonmail.com> (raw)
In-Reply-To: <9fb60e57ba5ed684c5ad113c3b9861e7d2e922e0.camel@gmail.com>
Hi,
Yes I'm still interested in upstreaming this package. True, in the meantime a lot has happened and I'll prepare a patch with simplified inputs and Gexps.
Also the databases will be in separate packages and just put into the inputs and linked correctly.
And I'll also update the package version.
Unfortunately HW issues will remain with us for long and it's useful to have some way to check for them.
FIY I'm currently also in process of packaging other stuff so it might take some time.
----
Petr
next prev parent reply other threads:[~2022-06-26 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 17:00 [bug#49898] [PATCH] gnu: Add spectre-meltdown-checker phodina via Guix-patches via
2021-08-06 13:58 ` Leo Prikler
2021-08-07 9:04 ` [bug#49898] [PATCH v2] " phodina via Guix-patches via
2021-08-07 9:50 ` Leo Prikler
2021-08-08 11:05 ` [bug#49898] [PATCH v3] " phodina via Guix-patches via
2021-08-08 21:42 ` Leo Prikler
2021-09-18 15:25 ` [bug#49898] [PATCH v4] " phodina via Guix-patches via
2021-09-18 17:03 ` Liliana Marie Prikler
2021-12-07 22:04 ` [bug#49898] [PATCH v5] " phodina via Guix-patches via
2022-06-26 10:23 ` Liliana Marie Prikler
2022-06-26 11:07 ` phodina via Guix-patches via [this message]
2022-07-01 21:57 ` [bug#49898] [PATCH v6] " phodina via Guix-patches via
2022-07-01 23:02 ` Liliana Marie Prikler
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='MDXych3ebMv3NuAgJgpGtQ68v2qK_c7YCVZnGR0rVKkymTzHzqZ6um7eS_MVxV3Y862FQ2UVc7D5cQrsCxNkq4eu7tf9iYzcvxnxPPFqNbY=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=49898@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=phodina@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 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).