From: Willy Tarreau <w@1wt.eu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Dave Jones <davej@redhat.com>, Andi Kleen <andi@firstfloor.org>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>
Subject: Re: [PATCH] Delete obsolete RAW driver feature.
Date: Thu, 22 Mar 2007 00:24:33 +0100 [thread overview]
Message-ID: <20070321232433.GX943@1wt.eu> (raw)
In-Reply-To: <20070321161341.0f87ed60.akpm@linux-foundation.org>
On Wed, Mar 21, 2007 at 04:13:41PM -0700, Andrew Morton wrote:
> On Thu, 22 Mar 2007 00:10:50 +0000
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
> > > > This is a user visible API it is therefore not elligable for removal
> > > > anyway
> > >
> > > mutter.
> > >
> > > We've given people years of notice and _some_ applications have converted
> > > over to open("/dev/sda1", O_DIRECT), as they should.
> >
> > Linus said we don't break old applications by removing APIs. People
> > believe him.
> >
>
> That's just dogma, and not credible dogma at that. We regularly remove
> features and we have processes for this.
>
> There is no reason why we cannot, with sufficient effort, remove this
> driver at some time in the future.
Then a printk() on every open() should be enough. We've all been seeing
"Warning: tcpdump uses obsolete AF_PACKET"... and it finally disappeared.
It's a slow but necessary process IMHO. I agree with Alan that it's not
nice for the users to have sudden application errors without enough earlier
notification (not everybody reads sources for removal notifications).
Regards,
Willy
next prev parent reply other threads:[~2007-03-21 23:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 11:59 [PATCH] Delete obsolete RAW driver feature Robert P. J. Day
2007-03-18 15:57 ` Andi Kleen
2007-03-18 15:38 ` Robert P. J. Day
2007-03-20 16:57 ` Dave Jones
2007-03-20 18:14 ` Alan Cox
2007-03-20 18:47 ` Robert P. J. Day
2007-03-21 22:19 ` Andrew Morton
2007-03-21 23:19 ` Dave Jones
2007-03-21 23:27 ` Andrew Morton
2007-03-21 23:42 ` Dave Jones
2007-03-21 23:56 ` Andrew Morton
2007-03-22 0:10 ` Alan Cox
2007-03-21 23:13 ` Andrew Morton
2007-03-21 23:24 ` Willy Tarreau [this message]
2007-03-21 23:43 ` Dave Jones
2007-03-22 4:12 ` Willy Tarreau
2007-03-22 4:17 ` Dave Jones
2007-03-22 4:45 ` Willy Tarreau
2007-03-22 5:02 ` Dave Jones
2007-03-22 5:53 ` Willy Tarreau
2007-03-22 6:10 ` Dave Jones
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=20070321232433.GX943@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=bunk@stusta.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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;
as well as URLs for NNTP newsgroup(s).