From: Dave Jones <davej@redhat.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Adrian Bunk <bunk@kernel.org>,
perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] unexport sys_{open,read}
Date: Tue, 25 Sep 2007 17:17:44 -0400 [thread overview]
Message-ID: <20070925211744.GM8127@redhat.com> (raw)
In-Reply-To: <20070910161456.7431312c@laptopd505.fenrus.org>
On Mon, Sep 10, 2007 at 04:14:56PM +0100, Arjan van de Ven wrote:
> Maybe I'm too pessimistic in my assumption that external open module
> writers don't actually follow mainline closely; and maybe part of me
> would love for them to follow it closer, so close that they would even
> consider submitting their driver for it. But sadly from experience...
> warnings dont' work. Only when things break hard people notice.
We've both done the same job, so it's unsurprising that we share the
same view on this. A number of times I've had out of tree module
authors complaining to _me_ because "Fedora fucked up my module, it
works fine in $otherdistro" (ignoring the fact that $otherdistro
is a point release or more behind Fedora).
There's definitly a culture-gap between some out-of-tree module
authors and people who intend from day 1 to get their code merged
into mainline. The former don't know what happens in mainline
until several distros start moving onto newer kernels, so no amount
of warnings is going to help these people.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-09-25 21:19 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
2007-09-10 22:56 ` Rene Herman
2007-09-10 15:14 ` Arjan van de Ven
2007-09-25 21:17 ` Dave Jones [this message]
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=20070925211744.GM8127@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.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