From: Andrew Morton <akpm@osdl.org>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, torvalds@osdl.org
Subject: Re: RFC: what's in a stable series?
Date: Wed, 9 Jul 2003 21:16:45 -0700 [thread overview]
Message-ID: <20030709211645.40353fc2.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.55L.0307100040271.6629@freak.distro.conectiva>
Marcelo Tosatti <marcelo@conectiva.com.br> wrote:
>
> Its a case-by-case problem.
It is. Generally I think we should prefer to do the right thing rather
than adhering to the old API out of some principle.
Evaluate the impact on out-of-tree kernel patches (especially vendor
kernels) and if it is unacceptable then reject the change or augment the API
rather than changing it.
> I reverted the direct IO patches because hch complained on me that they
> change the direct IO API, and we really dont want that kind of
> change, IMHO.
OK, we're on to a specific case. Albeit a very small one.
I think Trond's direct IO change was right. The impact on out-of-tree code
is infinitesimal. Stick a #define O_DIRECT_NEEDS_A_FILP in the header and
let the XFS guys write a four-line patch. There's no point in mucking up
the kernel API to save such a small amount of work.
Or merge XFS.
next prev parent reply other threads:[~2003-07-10 4:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 1:06 RFC: what's in a stable series? Jeff Garzik
2003-07-10 1:08 ` Jeff Garzik
2003-07-10 3:34 ` Herbert Pötzl
2003-07-10 7:53 ` Christoph Hellwig
2003-07-10 11:22 ` Alan Cox
2003-07-10 12:36 ` Herbert Pötzl
2003-07-10 3:54 ` Greg KH
2003-07-10 3:54 ` Marcelo Tosatti
2003-07-10 4:16 ` Andrew Morton [this message]
2003-07-10 7:53 ` Christoph Hellwig
2003-07-10 8:25 ` Andrew Morton
2003-07-10 7:53 ` Christoph Hellwig
2003-07-10 11:19 ` Alan Cox
2003-07-10 12:13 ` Marcelo Tosatti
2003-07-10 12:42 ` Alan Cox
2003-07-10 15:15 ` Christoph Hellwig
2003-07-10 19:00 ` Jan Kara
2003-07-11 8:36 ` Christoph Hellwig
2003-07-11 9:21 ` Alan Cox
2003-07-10 15:12 ` Christoph Hellwig
2003-07-10 15:11 ` Christoph Hellwig
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=20030709211645.40353fc2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@osdl.org \
/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