From: Jeff Garzik <jgarzik@pobox.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: 2.4 direct_IO API changing?
Date: Sun, 06 Jul 2003 15:11:40 -0400 [thread overview]
Message-ID: <3F08746C.6010803@pobox.com> (raw)
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.
Jeff
next reply other threads:[~2003-07-06 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 19:11 Jeff Garzik [this message]
2003-07-06 20:03 ` 2.4 direct_IO API changing? Alan Cox
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=3F08746C.6010803@pobox.com \
--to=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