From: Zheng Junjie <zhengjunjie@iscas.ac.cn>
To: Wilko Meyer <w@wmeyer.eu>
Cc: Guillaume Le Vaillant <glv@posteo.net>,
71372@debbugs.gnu.org, me@tobias.gr, leo@famulari.name
Subject: [bug#71372] [PATCH] gnu: linux-libre: Add 6.9-riscv.conf
Date: Tue, 18 Jun 2024 00:26:35 +0800 [thread overview]
Message-ID: <87wmmn4jt0.fsf@iscas.ac.cn> (raw)
In-Reply-To: <87ikymyoc5.fsf@wmeyer.eu> (Wilko Meyer's message of "Thu, 06 Jun 2024 19:26:34 +0200")
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Wilko Meyer <w@wmeyer.eu> writes:
> Hi,
>
> Zheng Junjie <zhengjunjie@iscas.ac.cn> writes:
>
>> Keep open to discuss missing riscv kernel configuration.
>
> I think it's feasible to ship a riscv kernel configuration for new major
> kernel releases (will do that from now on when packaging new major
> versions) as well as adding one to all currently supported kernels (have
> to see wether I'll find time to do that during the next days). As I don't
i think we just need add new riscv kernel configurations on linux 6.6
(many vendor riscv kernel will base on it) and latest version.
> have any riscv hardware available to test configurations on, I can't
> guarantee that the config will be entirely usable though.
for now, i think it is normal to lose most features.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2024-06-17 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 6:16 [bug#71372] [PATCH] gnu: linux-libre: Add 6.9-riscv.conf Zheng Junjie
2024-06-05 7:34 ` Guillaume Le Vaillant
2024-06-06 5:45 ` Zheng Junjie
2024-06-06 8:58 ` Guillaume Le Vaillant
2024-06-06 10:43 ` Zheng Junjie
2024-06-06 17:26 ` Wilko Meyer
2024-06-17 16:26 ` Zheng Junjie [this message]
2024-06-13 11:54 ` Guillaume Le Vaillant
2024-06-17 16:29 ` bug#71372: " Zheng Junjie
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=87wmmn4jt0.fsf@iscas.ac.cn \
--to=zhengjunjie@iscas.ac.cn \
--cc=71372@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=leo@famulari.name \
--cc=me@tobias.gr \
--cc=w@wmeyer.eu \
/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).