From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v2] linux-mod-r1.eclass: new eclass, rewrite of linux-mod.eclass
Date: Mon, 29 May 2023 09:10:44 -0400 [thread overview]
Message-ID: <ZHSkVNT6iu74Nntu@eversor> (raw)
In-Reply-To: <20230528124116.7019-1-ionen@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Sun, May 28, 2023 at 08:41:16AM -0400, Ionen Wolkens wrote:
> Likely final as far as initial merge goes.
>
> Given been suggested that it'd be easier to have it in the tree for
> testing and that without consumers it can't break anything (yet),
> planning to merge tomorrow. Just posting update here as a formality.
It is now merged with just a few minor comment/doc adjustments on top
(no code changes).
Feel free to start using it with in-tree ebuilds (currently used
by app-admin/ryzen_smu and games-util/xpadneo). Should still be
considered experimental as it had very little reviewing and testing
so far (please report issues!).
linux-mod-r0 will likely be marked @DEPRECATED at a later date.
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-05-29 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 4:02 [gentoo-dev] [PATCH 0/4] linux-mod-r1.eclass: new eclass, rewrite of -r0 Ionen Wolkens
2023-05-26 4:02 ` [gentoo-dev] [PATCH 1/4] profiles/use.desc: create USE=strip global USE flag Ionen Wolkens
2023-05-26 5:06 ` Sam James
2023-05-26 5:25 ` Ionen Wolkens
2023-05-26 4:02 ` [gentoo-dev] [PATCH 2/4] profiles/use.desc: create USE=modules-sign " Ionen Wolkens
2023-05-26 4:02 ` [gentoo-dev] [PATCH 3/4] linux-mod-r1.eclass: new eclass, rewrite of linux-mod.eclass Ionen Wolkens
2023-05-28 12:41 ` [gentoo-dev] [PATCH v2] " Ionen Wolkens
2023-05-29 13:10 ` Ionen Wolkens [this message]
2023-05-26 4:02 ` [gentoo-dev] [PATCH 4/4] app-admin/ryzen_smu: migrate to linux-mod-r1 Ionen Wolkens
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=ZHSkVNT6iu74Nntu@eversor \
--to=ionen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox