From: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] ["PATCH"] Linus breaks virtualbox-modules
Date: Fri, 22 Feb 2013 11:27:45 +0100 [thread overview]
Message-ID: <51274821.E65Tn+F6dPAxgKzU%Joerg.Schilling@fokus.fraunhofer.de> (raw)
In-Reply-To: <CAOazyz2DQYQ0sTS-je9VuiRQpTXj2N5Lr0+pCfyLGYwVcNf7Kg@mail.gmail.com>
Alon Bar-Lev <alonbl@gentoo.org> wrote:
> On Thu, Feb 21, 2013 at 12:00 PM, Joerg Schilling
> <Joerg.Schilling@fokus.fraunhofer.de> wrote:
> > Mike Gilbert <floppym@gentoo.org> wrote:
> > At that time it turned out, that Linus does not seem to be able to understand
> > what changes may break an interface. The real problem however was that he was
> > not willing to fix his fault, so we can definitely call this case (from Spring
> > 2004) a break by intention.
>
> You are totally confusing between stable user space interfaces and
> unstable kernel interfaces.
> Kernel is allowed to evolve without legacy and breaking whatever
> needed in order to be in better shape. Whoever writes external module
> should merge it into mainline or rebase every release.
Well, it seemt that you are confusing user-interfaces with kernel-internal-interfaces :-(
I was of course writing about a kernel <-> user interface that need to stay
stable as the problem has been identified with cdrtools and cdrtools are known to run
in user space.
It seems however, that you have similar problems as Linus. Linus believes that
user level code is not allowed to include include files from the kernel that
describe kernel <-> user interfaces. With this rule, he disallows kernel <-> user
interfaces to be used at all - which looks really strange.
Jörg
--
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni)
joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
next prev parent reply other threads:[~2013-02-22 10:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 13:40 [gentoo-user] ["PATCH"] Linus breaks virtualbox-modules walt
2013-02-20 14:04 ` Michael Hampicke
2013-02-20 20:23 ` Markos Chandras
2013-02-20 20:57 ` Mike Gilbert
2013-02-21 1:15 ` [gentoo-user] " walt
2013-02-21 1:53 ` Mike Gilbert
2013-02-21 2:33 ` Pandu Poluan
2013-02-21 10:00 ` [gentoo-user] " Joerg Schilling
2013-02-21 20:15 ` Bruce Hill
2013-02-22 5:30 ` Alon Bar-Lev
2013-02-22 10:27 ` Joerg Schilling [this message]
2013-02-22 21:44 ` Bruce Hill
2013-02-22 21:45 ` Bruce Hill
2013-02-21 8:30 ` Helmut Jarausch
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=51274821.E65Tn+F6dPAxgKzU%Joerg.Schilling@fokus.fraunhofer.de \
--to=joerg.schilling@fokus.fraunhofer.de \
--cc=gentoo-user@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