public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tonnerre <tonnerre@thundrix.ch>
To: Olivier Galibert <galibert@pobox.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: __initcall macros and C token pasting
Date: Sun, 26 Sep 2004 19:24:29 +0200	[thread overview]
Message-ID: <20040926172429.GA15441@thundrix.ch> (raw)
In-Reply-To: <20040926172104.GA44528@dspnet.fr.eu.org>

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

Salut,

On Sun, Sep 26, 2004 at 07:21:04PM +0200, Olivier Galibert wrote:
> > One response is to build a stable API for the core.
> 
> This has absolutely zero chance to happen, as the evolution of the
> kernel has proven time and again.  The internal APIs of the kernel
> aren't stable, however much we'd like them to be, because the best way
> to do something at time t isn't the best way to do it at time t+1.
> The best that is done is to try to change the drivers at the time the
> core changes, and that only happens if the source of the drivers is
> there along with the rest of the kernel.

That'd be true if fact were fiction and TV reality.

Actually, lots  of drivers  that *are* in  the kernel are  pretty much
broken.

And I don't  think putting more drivers into  the mainline kernel will
fix this problem.

The  only thing that  will is  doing stable  and development  trees in
different places. We ceased to do that, and *it's* *no* *good*.

			    Tonnerre

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-09-26 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-25 17:57 __initcall macros and C token pasting Jon Smirl
2004-09-25 18:32 ` viro
2004-09-25 18:40   ` Jon Smirl
2004-09-25 19:17   ` Jon Smirl
2004-09-26 17:21     ` Olivier Galibert
2004-09-26 17:24       ` Tonnerre [this message]
2004-09-26 17:42         ` Christoph Hellwig
2004-09-26 19:56         ` Geert Uytterhoeven

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=20040926172429.GA15441@thundrix.ch \
    --to=tonnerre@thundrix.ch \
    --cc=galibert@pobox.com \
    --cc=linux-kernel@vger.kernel.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