public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tobias Powalowski <t.powa@gmx.de>, Takashi Iwai <tiwai@suse.de>,
	Christoph Hellwig <hch@infradead.org>,
	Zachary Amsden <zach@vmware.com>
Subject: Re: [PATCH] x86/paravirt: revert exports to restore old behaviour
Date: Thu, 29 Nov 2007 23:06:10 +0100	[thread overview]
Message-ID: <20071129220610.GK29463@stusta.de> (raw)
In-Reply-To: <474E007B.1020405@goop.org>

On Wed, Nov 28, 2007 at 03:57:47PM -0800, Jeremy Fitzhardinge wrote:
> Adrian Bunk wrote:
> > This does not apply since we do not have a stable in-kernel API, and 
> > therefore changes to the in-kernel API can by definition not be 
> > regressions.
> >
> > 2.6.24 most likely contains hundreds of changes and removals of 
> > in-kernel APIs that existed in 2.6.23.
> >
> > Are you seriously suggesting that e.g. every single change to any struct 
> > under include/ [1] would require an announcement x kernel releases 
> > before it can be implemented?
> 
> Well, no, but that's not the point.
>...

Sorry if I was a bit harsh, but no change to the in-kernel API [1] 
could ever be called a regression since we do not have a stable 
in-kernel API.

And what annoyed was that this was one of at least 3 ongoing 
linux-kernel threads where people tried to bring the notion that any 
part of the in-kernel API had any kind of stability.

>     J

cu
Adrian

[1] and that includes what is visible to modules

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-11-29 22:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 22:57 [PATCH] x86/paravirt: revert exports to restore old behaviour Jeremy Fitzhardinge
2007-11-28 20:40 ` Adrian Bunk
2007-11-28 21:15   ` Jeremy Fitzhardinge
2007-11-28 22:39     ` Adrian Bunk
2007-11-28 23:57       ` Jeremy Fitzhardinge
2007-11-29 22:06         ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-13 10:39 REGRESSION: 2.6.24 breaks nvidia and amd/ati binary drivers, by exporting paravirt symbols as GPL Tobias Powalowski
2007-11-13 20:21 ` [PATCH] x86/paravirt: revert exports to restore old behaviour Jeremy Fitzhardinge
2007-11-13 22:22   ` Christoph Hellwig
2007-11-14  0:51     ` Zachary Amsden
2007-11-19 17:05       ` Takashi Iwai
2007-11-20  1:14         ` Jeremy Fitzhardinge
2007-11-20  6:25           ` Takashi Iwai
2007-11-14  1:22     ` Jeremy Fitzhardinge

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=20071129220610.GK29463@stusta.de \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=t.powa@gmx.de \
    --cc=tiwai@suse.de \
    --cc=zach@vmware.com \
    /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