From: Adrian Bunk <bunk@fs.tum.de>
To: Christoph Hellwig <hch@lst.de>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make <linux/blk.h> obsolete
Date: Thu, 1 May 2003 20:47:01 +0200 [thread overview]
Message-ID: <20030501184700.GD21168@fs.tum.de> (raw)
In-Reply-To: <20030501204012.A16641@lst.de>
On Thu, May 01, 2003 at 08:40:12PM +0200, Christoph Hellwig wrote:
> On Thu, May 01, 2003 at 08:38:04PM +0200, Adrian Bunk wrote:
> > On Thu, May 01, 2003 at 08:07:19PM +0200, Christoph Hellwig wrote:
> > >...
> > > +/* this file is obsolete, please use <linux/blkdev.h> instead */
> > >...
> >
> > #warning linux/blk.h is deprecated, use linux/blkdev.h instead.
> > #include <linux/blkdev.h>
> >
> > or simply remove the blk.h and fix all files trying to include it?
>
> Later. First thing is to kill the content, next the users.
> Adding the warning now would make a normal compile very verbose..
Shall I prepare a patch removing all #include <linux/blk.h>'s?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-05-01 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 18:07 [PATCH] make <linux/blk.h> obsolete Christoph Hellwig
2003-05-01 18:38 ` Adrian Bunk
2003-05-01 18:40 ` Christoph Hellwig
2003-05-01 18:47 ` Adrian Bunk [this message]
2003-05-01 18:48 ` Christoph Hellwig
2003-05-02 20:50 ` Adrian Bunk
2003-05-01 18:52 ` Andreas Dilger
2003-05-01 20:00 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2003-05-04 18:30 Christoph Hellwig
2003-05-08 2:57 Perez-Gonzalez, Inaky
2003-05-08 5:09 ` 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=20030501184700.GD21168@fs.tum.de \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.