From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Adrian Bunk <bunk@kernel.org>,
perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] unexport sys_{open,read}
Date: Mon, 10 Sep 2007 02:23:24 -0700 [thread overview]
Message-ID: <20070910022324.c69e1897.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070910090808.GA31204@infradead.org>
On Mon, 10 Sep 2007 10:08:08 +0100 Christoph Hellwig <hch@infradead.org> wrote:
> On Sun, Sep 09, 2007 at 02:59:40PM -0700, Andrew Morton wrote:
> > Sure. But I think it is better to give people some warning when we're
> > planning on breaking out-of-tree things. I do occasionally receive reports
> > of "hey, the X driver which I get from Y doesn't work any more". Often
> > it's open-source stuff, too. I see no point in irritating our users more than
> > we need to.
>
> There is no fucking reason they should have used it in the first place.
fucking except fucking we fucking exported fucking it fucking so fucking
they fucking used fucking it. fucking.
Hey, this would be easier with a sed script! And it so improves the
communication!
> Until we have something like a coherent export API instead of random crap
> exported because someone once needed it to do a dumb thing it'll happen.
> Only way to avoid it is to merge the driver and shake out their dumb ideas
> in the review process.
Well that's why I agreed that we should remove those exports.
> > 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.
>
> And I think almost everyone disagrees with you. We just carry too much
> crap around because of your subborness in this issue, and it gets really
> annoying to have some high up on the food chain fighting his longly flight
> against the other people.
I would like to see "everyone" explain what we lose by giving developers a
bit of warning before we break their stuff.
And it would need to be a good explanation, Christoph. A measured one
which recognises and then weighs the tradeoffs involved, and the costs. An
inebriated-sounding rant will not impress, sorry.
next prev parent reply other threads:[~2007-09-10 9:24 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 [this message]
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=20070910022324.c69e1897.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bunk@kernel.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