From: Jens Axboe <axboe@suse.de>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Christoph Hellwig <hch@lst.de>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [2.5 patch] remove all #include <blk.h>'s
Date: Sun, 11 May 2003 15:57:36 +0200 [thread overview]
Message-ID: <20030511135736.GM837@suse.de> (raw)
In-Reply-To: <20030510163043.GJ1107@fs.tum.de>
On Sat, May 10 2003, Adrian Bunk wrote:
> all #include <blk.h>'s for 2.5 and blk.h does now #error. If people
I think that's _really_ stupid. Make it a warning ala
#warning blk.h is deprecated, use blkdev.h
like we did with malloc.h in 2.4.
> want their drivers to run unmodified under 2.4 it might be necessary to
> do a
> #if LINUX_VERSION_CODE < KERNEL_VERSION(2,5,70)
> #include <linux/blk.h>
> #endif
That is horrible.
--
Jens Axboe
next prev parent reply other threads:[~2003-05-11 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 16:30 [2.5 patch] remove all #include <blk.h>'s Adrian Bunk
2003-05-10 16:57 ` Adrian Bunk
2003-05-11 13:57 ` Jens Axboe [this message]
2003-05-11 14:45 ` Adrian Bunk
2003-05-11 14:47 ` Jens Axboe
2003-05-27 22:06 Adrian Bunk
2003-07-03 23:22 Adrian Bunk
2003-07-15 15:34 Adrian Bunk
2003-07-15 19:39 ` Andrew Morton
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=20030511135736.GM837@suse.de \
--to=axboe@suse.de \
--cc=bunk@fs.tum.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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).