From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: "56200@debbugs.gnu.org" <56200@debbugs.gnu.org>
Subject: [bug#56200] Kernel 5.18 update
Date: Sun, 26 Jun 2022 14:57:12 +0000 [thread overview]
Message-ID: <uoh9pDIynMmDJ52_ik9bZbQttE3Jg3MP7FfuComfi-H_4LFcrrWfz8BfrGP2T7b5d7x5WVnjSF3hZiBBheMnrx1egcbl74nM_Ph23VubiD0=@protonmail.com> (raw)
In-Reply-To: <DEEquPRlhugDg1QJgv3If9HrQcPoXKYdh51WA8mMu-XQvdj2GJS4x3w2ZCpsVZTkR8ninRa74sfOiR_gPqdAGd1dhIX4bTvc69b-nR11W4k=@protonmail.com>
Hi Leo,
(I didn't get your message through email, just happened to see it on the issue browser.)
You want the config change to be part of the kernel update patch, and just on the x86_64 config? Or should it be a separate patch just changing that line in the config?
Thanks,
John
next prev parent reply other threads:[~2022-06-26 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 17:38 [bug#56200] Kernel 5.18 update Leo Famulari
2022-06-24 17:41 ` [bug#56200] [PATCH 1/3] gnu: Add linux-libre 5.18 Leo Famulari
2022-06-24 17:41 ` [bug#56200] [PATCH 2/3] gnu: linux-libre: Update to 5.18.6 Leo Famulari
2022-06-24 17:41 ` [bug#56200] [PATCH 3/3] gnu: Remove linux-libre 5.17 Leo Famulari
2022-06-24 18:25 ` [bug#56200] Kernel 5.18 update John Kehayias via Guix-patches via
2022-06-24 18:49 ` Leo Famulari
2022-06-26 14:57 ` John Kehayias via Guix-patches via [this message]
2022-06-26 20:02 ` Leo Famulari
2022-06-26 20:30 ` Tobias Geerinckx-Rice via Guix-patches via
2022-06-27 4:43 ` [bug#56200] [PATCH 4/4] linux-libre: Enable the AMD HSA driver John Kehayias via Guix-patches via
2022-06-28 20:30 ` Leo Famulari
2022-06-29 0:38 ` [bug#56200] [PATCH v2] gnu: " John Kehayias via Guix-patches via
2022-06-29 1:05 ` Leo Famulari
2022-06-29 12:55 ` bug#56200: " Leo Famulari
2022-06-29 16:17 ` [bug#56200] " John Kehayias via Guix-patches via
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='uoh9pDIynMmDJ52_ik9bZbQttE3Jg3MP7FfuComfi-H_4LFcrrWfz8BfrGP2T7b5d7x5WVnjSF3hZiBBheMnrx1egcbl74nM_Ph23VubiD0=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=56200@debbugs.gnu.org \
--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 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).