From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: torvalds@transmeta.com, hch@infradead.org,
linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: [2.5 patch] remove all #include <blk.h>'s
Date: Tue, 15 Jul 2003 12:39:35 -0700 [thread overview]
Message-ID: <20030715123935.3500a6cc.akpm@osdl.org> (raw)
In-Reply-To: <20030715153458.GK10191@fs.tum.de>
Adrian Bunk <bunk@fs.tum.de> wrote:
>
> the attached patch against 2.6.0-test1 (gzip'ed due to it's size) causes
> blk.h to print a warning and removes all uses of blk.h. I've tested the
> compilation in 2.6.0-test1 with a .config that tries to compile as many
> drivers as possible.
>
> Please either apply it or send a short note that you don't want to apply
> it.
"cleanups" are being vigorously ignored now. I'd be inclined to let this
one go, thanks.
next prev parent reply other threads:[~2003-07-15 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 15:34 [2.5 patch] remove all #include <blk.h>'s Adrian Bunk
2003-07-15 19:39 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-03 23:22 Adrian Bunk
2003-05-27 22:06 Adrian Bunk
2003-05-10 16:30 Adrian Bunk
2003-05-10 16:57 ` Adrian Bunk
2003-05-11 13:57 ` Jens Axboe
2003-05-11 14:45 ` Adrian Bunk
2003-05-11 14:47 ` Jens Axboe
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=20030715123935.3500a6cc.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=akpm@digeo.com \
--cc=bunk@fs.tum.de \
--cc=hch@infradead.org \
--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