all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 74778@debbugs.gnu.org
Subject: [bug#74778] [PATCH v3] gnu: linux-libre: Enable simpledrm driver.
Date: Wed, 1 Jan 2025 16:40:33 -0500	[thread overview]
Message-ID: <Z3W2UfPbxbswIPuO@jasmine.lan> (raw)
In-Reply-To: <871pxmmu4y.fsf@nckx>

On Wed, Jan 01, 2025 at 04:27:41PM +0100, Tobias Geerinckx-Rice wrote:
> Polite nack.

[...]

> 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.

Thanks for chiming in Tobias. I thought these options sounded familiar
and hoped it wasn't a rehash of this old issue. I do seem to remember
that we had, basically, traded one form of breakage for another.

> Aside: why do we keep adding DEFAULT-EXTRA-LINUX-OPTIONS instead of
> modifying the configuration files themselves?  Maybe this is a separate
> discussion.

I think that modifying the config files is better because, while doing
so, the combination of options is properly set by the kernel
configuration machinery and, at the end of the process, we have a
config that can be inspected to check for a sensible outcome.

On the other hand, if we use the Scheme machinery, the final config file
is only created while building the kernel packages and we are less
likely to inspect it. Of course it's still possible to inspect
regardless of which method is used.

I'd suggest only using the Scheme interface to correct FSDG issues and
serious problems like that.

But, in a related aside where I zoom further out, we need more people
involved with the kernel packaging in order to get a really optimal
result. So I'm not too picky about details like this.




      reply	other threads:[~2025-01-01 21:41 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
2025-01-01 21:40       ` Leo Famulari [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z3W2UfPbxbswIPuO@jasmine.lan \
    --to=leo@famulari.name \
    --cc=74778@debbugs.gnu.org \
    --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.