From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4 direct_IO API changing?
Date: 06 Jul 2003 21:03:30 +0100 [thread overview]
Message-ID: <1057521807.1277.9.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3F08746C.6010803@pobox.com>
On Sul, 2003-07-06 at 20:11, Jeff Garzik wrote:
> I see in 2.4.22-BK-latest:
>
> > - int (*direct_IO)(int, struct inode *, struct kiobuf *, unsigned long, int);
> > + int (*direct_IO)(int, struct file *, struct kiobuf *, unsigned long, int
>
>
> Should this really be changing in the middle of a stable series?
>
> I realize that vendor's are already shipping this difference, but
> still... it's a bit of an abrupt midseries change that can potentially
> break working code.
Its something most people are already shipping and something you
actually do need for some of the direct IO stuff.
BTW: Marcelo your mail system is broken *again*
prev parent reply other threads:[~2003-07-06 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 19:11 Jeff Garzik
2003-07-06 20:03 ` Alan Cox [this message]
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=1057521807.1277.9.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®