From: marmeladema <marmeladema@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: kernel-libc-headers: update to 5.15.33
Date: Thu, 30 Jun 2022 08:50:19 +0200 [thread overview]
Message-ID: <20220630065019.AIGxBJh7EenUsYpG9K5QH5xea8GQhLUQLQ5ZqdAxNqc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36606@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
New comment by marmeladema on void-packages repository
https://github.com/void-linux/void-packages/pull/36606#issuecomment-1170835350
Comment:
It allows package that detect kernel features at build time to enable more recent functionality. Namely this can help enabling hardware video decoding with ffmpeg/gstreamer and the like.
But more generally, what is the policy for sticking with a relatively old UAPI? If it's because we allow people to install and use (very) old kernel version then we'll never be able to update the UAPI right? That sounds unfortunate
next prev parent reply other threads:[~2022-06-30 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 20:08 [PR PATCH] " marmeladema
2022-06-29 20:42 ` Duncaen
2022-06-30 1:36 ` ahesford
2022-06-30 6:50 ` marmeladema [this message]
2022-07-05 14:42 ` ahesford
2022-10-04 2:14 ` github-actions
2022-10-18 2:14 ` [PR PATCH] [Closed]: " github-actions
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=20220630065019.AIGxBJh7EenUsYpG9K5QH5xea8GQhLUQLQ5ZqdAxNqc@z \
--to=marmeladema@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).