From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Leo Famulari <leo@famulari.name>, 74778@debbugs.gnu.org
Subject: [bug#74778] [PATCH v3] gnu: linux-libre: Enable simpledrm driver.
Date: Wed, 01 Jan 2025 16:27:41 +0100 [thread overview]
Message-ID: <871pxmmu4y.fsf@nckx> (raw)
In-Reply-To: <Z3QePKMh1vVrQAcs@jasmine.lan> (Leo Famulari's message of "Tue, 31 Dec 2024 11:39:24 -0500")
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
Happy newest year, all!
Polite nack. Let's not make these same changes yet again without
better documenting our chosen combination and any accepted
trade-offs.
Otherwise, some frustratingly obtuse half-wit's only going to
revert them without a proper commit message to fix somebody's bug
only to re-enable them later to fix somebody's bug, probably:
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=1dfe8c372163d481ebebb97dd3b4cafa49906b28
…
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6d7e181ba18d11c92409a93936025fb46b9c8171
…
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=e49fdc231b0be00490fe1321888eb5c2acc480ac
I'll try to find the context for my reversion in my own logs, but
it surely broke something. There may be no way to support all
users.
I do urge people to test it on kernel-updates, but this is not a
simple ‘enable CONFIG_FOOBLES to get foobles!’ situation.
Aside: why do we keep adding DEFAULT-EXTRA-LINUX-OPTIONS instead
of modifying the configuration files themselves? Maybe this is a
separate discussion.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2025-01-01 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 5:49 [bug#74778] [PATCH] gnu: linux-libre: Enable simpledrm driver Homo via Guix-patches via
2024-12-16 9:03 ` [bug#74778] [PATCH v2] " Homo via Guix-patches via
2024-12-17 12:14 ` [bug#74778] [PATCH v3] " Homo via Guix-patches via
2024-12-31 16:39 ` Leo Famulari
2025-01-01 5:36 ` gay--- via Guix-patches via
2025-01-01 21:56 ` Leo Famulari
2025-01-02 5:52 ` gay--- via Guix-patches via
2025-01-02 18:58 ` Leo Famulari
[not found] ` <89b1b131aa04049887dc421d6c62db31@disroot.org>
2025-01-03 4:21 ` gay--- via Guix-patches via
2025-01-01 15:27 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2025-01-01 21:40 ` Leo Famulari
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=871pxmmu4y.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=74778@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=me@tobias.gr \
/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.