all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Dave Love <fx@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: why is linux-libre-headers behind linux-libre?
Date: Mon, 06 Nov 2017 14:22:50 -0500	[thread overview]
Message-ID: <87inengqk5.fsf@netris.org> (raw)
In-Reply-To: <87mv3zwi4m.fsf@albion.it.manchester.ac.uk> (Dave Love's message of "Mon, 06 Nov 2017 15:18:17 +0000")

Dave Love <fx@gnu.org> writes:

> Pjotr Prins <pjotr.public12@thebird.nl> writes:
>
>> The Linux kernel API is remarkably stable.
>
> Actually, I don't think that's the case, speaking as someone who's had
> to deal with out-of-tree drivers for various reasons.  For instance, the
> OrangeFS module typically broke when I tried to rebuild the package on a
> new version of Fedora.  Even RHEL can break such things with minor
> releases.

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.

      Mark

  reply	other threads:[~2017-11-06 19:23 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 [this message]
2017-11-06 21:00                 ` Pjotr Prins
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

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

  git send-email \
    --in-reply-to=87inengqk5.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=fx@gnu.org \
    --cc=guix-devel@gnu.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 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.