public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Rene Herman <rene.herman@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Al Viro <viro@ftp.linux.org.uk>,
	Christoph Hellwig <hch@infradead.org>,
	perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] unexport sys_{open,read}
Date: Tue, 11 Sep 2007 00:41:12 +0200	[thread overview]
Message-ID: <20070910224112.GK3563@stusta.de> (raw)
In-Reply-To: <46E5C21C.8040609@gmail.com>

On Tue, Sep 11, 2007 at 12:15:56AM +0200, Rene Herman wrote:
> On 09/11/2007 12:18 AM, Adrian Bunk wrote:
>
>> On Mon, Sep 10, 2007 at 01:17:59PM -0700, Andrew Morton wrote:
>
>>> There is no benefit in making some rigid set of rules.
>> Is is considered beneficial to provide API stability for external modules 
>> or not?
>
> If I may...
>
> Yes, it is. Just not at any significant cost and Andrew is saying that he 
> considers the _UNUSED() thing not significant.

But there is no API stability for external modules this way.

It simply doesn't make sense to give the few sys_open() abusers even 
more grace period while changes to the IRQ API affecting nearly everyone 
are allowed without any requirements of ensuring API stability.

I'm not a fan of API stability for external modules, but if API 
stability was considered important it should be done consequently and 
not only for some patches that have the bad fate of having to go through 
Andrew to Linus.

> Rene.

cu
Adrian

-- 

       "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-09-10 22:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-09 20:25 [-mm patch] unexport sys_{open,read} Adrian Bunk
2007-09-09 20:39 ` Christoph Hellwig
2007-09-09 21:59   ` Andrew Morton
2007-09-09 22:22     ` Adrian Bunk
2007-09-09 22:41       ` Arjan van de Ven
2007-09-09 23:18         ` Adrian Bunk
2007-09-10  9:08     ` Christoph Hellwig
2007-09-10  9:23       ` Andrew Morton
2007-09-10 12:03         ` Adrian Bunk
2007-09-10 12:31         ` Alan Cox
2007-09-10 12:43         ` Al Viro
2007-09-10 17:25           ` Andrew Morton
2007-09-10 17:44             ` Alan Cox
2007-09-10 17:54               ` Andrew Morton
2007-09-13 23:23                 ` Greg KH
2007-09-10 19:58             ` Adrian Bunk
2007-09-10 20:17               ` Andrew Morton
2007-09-10 22:18                 ` Adrian Bunk
2007-09-10 22:15                   ` Rene Herman
2007-09-10 22:41                     ` Adrian Bunk [this message]
2007-09-10 22:56                       ` Rene Herman
2007-09-10 15:14         ` Arjan van de Ven
2007-09-25 21:17           ` Dave Jones
2007-09-10 12:18   ` David Miller
2007-09-10 12:21     ` Christoph Hellwig
2007-09-18 14:10     ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2007-08-22  9:06 2.6.23-rc3-mm1 Andrew Morton
2007-08-27 21:27 ` [-mm patch] unexport sys_{open,read} Adrian Bunk
2007-08-27 22:53   ` Arjan van de Ven
2007-08-27 23:17     ` Adrian Bunk

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=20070910224112.GK3563@stusta.de \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --cc=rene.herman@gmail.com \
    --cc=viro@ftp.linux.org.uk \
    /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