From: Adrian Bunk <bunk@kernel.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] unexport sys_{open,read}
Date: Mon, 10 Sep 2007 01:18:45 +0200 [thread overview]
Message-ID: <20070909231845.GC3563@stusta.de> (raw)
In-Reply-To: <20070909234118.43d75f6f@laptopd505.fenrus.org>
On Sun, Sep 09, 2007 at 11:41:18PM +0100, Arjan van de Ven wrote:
> On Mon, 10 Sep 2007 00:22:03 +0200
> Adrian Bunk <bunk@kernel.org> wrote:
>
> > On Sun, Sep 09, 2007 at 02:59:40PM -0700, Andrew Morton wrote:
> > > On Sun, 9 Sep 2007 21:39:20 +0100 Christoph Hellwig
> > > <hch@infradead.org> wrote:
>
> > > Adrian knows this, yet he habitually sends zero-warning
> > > export-removal patches and I habitually ignore them. I guess we
> > > must both enjoy this or something.
> >
> > You might rename EXPORT_UNUSED_SYMBOL to EXPORT_UNUSED_SYMBOL_ADRIAN
> > because AFAIK I am still the only person who was ever dumb enough to
> > use it after you wanted me to do so...
> >
> > Everyone else is allowed to always add, remove and change exports
> > as he likes, but I should go through this special process.
> >
> > It makes no sense (except for keeping me busy) to treat some patches
> > I send special while changes made by other people that break the
> > modules API are still allowed.
> >
> > Andrew, please define API rules, IOW rules for addition, removal and
> > changing of exported code, that are valid for *everyone* or go to
> > hell with your EXPORT_UNUSED_SYMBOL.
>
>
> Adrian,
>
> as much as I personally disagree with Andrew's policy here (esp for
> these symbols, they have been deprecated for years now), it's trivial
> to just follow his requirements and get this over with.
>...
Andrew wants a deprecation period for these symbols where the few users
are most likely doing something wrong when using them, but if someone
e.g. changes the IRQ API in a way that breaks most external modules no
deprecation period is required.
If the kernel should get some module API stability processes like
EXPORT_UNUSED_SYMBOL() deprecation periods have to be made mandatory
for *all* API changes and removals.
But forcing EXPORT_UNUSED_SYMBOL on me while allowing other people to do
bigger API changes without deprecation periods is not a policy, it's a
personal offence.
> Greetings,
> Arjan van de Ven
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
next prev parent reply other threads:[~2007-09-09 23:18 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 [this message]
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
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=20070909231845.GC3563@stusta.de \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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