From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>, Dave Love <fx@gnu.org>
Subject: Re: why is linux-libre-headers behind linux-libre?
Date: Mon, 6 Nov 2017 22:00:52 +0100 [thread overview]
Message-ID: <20171106210052.GA27263@thebird.nl> (raw)
In-Reply-To: <87inengqk5.fsf@netris.org>
On Mon, Nov 06, 2017 at 02:22:50PM -0500, Mark H Weaver wrote:
> When Pjotr said that the Linux API is remarkably stable, I assume he was
> talking about the syscall API, i.e. the API available to programs run in
> user space. The Linux kernel project has a strict policy to avoid
> changing its API in a way that would break user programs.
>
> The internal API available to kernel modules and drivers is another
> matter entirely. The Linux kernel project reserves the right to change
> that internal API freely, and does so regularly.
Right, and libre-headers should follow that kernel version. In other
words, for the generic case any version of libre-headers will work. I
am not talking about device drivers etc.
Pj.
--
next prev parent reply other threads:[~2017-11-06 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 12:35 why is linux-libre-headers behind linux-libre? Dave Love
2017-10-31 13:00 ` Vincent Legoll
2017-10-31 19:38 ` Efraim Flashner
2017-11-02 10:16 ` Dave Love
2017-11-05 15:51 ` Ludovic Courtès
2017-11-06 8:44 ` Mark H Weaver
2017-11-06 8:51 ` Pjotr Prins
2017-11-06 15:18 ` Dave Love
2017-11-06 19:22 ` Mark H Weaver
2017-11-06 21:00 ` Pjotr Prins [this message]
2017-11-07 9:56 ` Ludovic Courtès
2017-11-06 15:16 ` Dave Love
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=20171106210052.GA27263@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=fx@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
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).