From: Carlo Wood <carlo@alinoe.com>
To: spse@secret.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Compile error blkmtd.c, v2.5.70 (and smaller)
Date: Fri, 6 Jun 2003 15:07:47 +0200 [thread overview]
Message-ID: <20030606130747.GA9861@alinoe.com> (raw)
kernel 2.5.70,
drivers/mtd/devices/blkmtd.c
still contains
#include <linux/iobuf.h>
reason enough not to compile...
that file was removed from 2.5.
I am suprised that this file was apparently never compiled by people :/
Commands used to backup/check my statement:
/usr/src/linux-2.5.69>grep -Hn iobuf.h drivers/mtd/devices/blkmtd.c
drivers/mtd/devices/blkmtd.c:52:#include <linux/iobuf.h>
/usr/src/linux-2.5.69>find . -type f -exec grep -H 'iobuf\.h' {} \;
./drivers/mtd/devices/blkmtd.c:#include <linux/iobuf.h>
/usr/src/linux-2.5.69>find . -name 'iobuf.h'
/usr/src/linux-2.5.69>find . -name '*iobuf*'
/usr/src/linux-2.5.69>
/usr/src/linux-2.5.69>locate iobuf.h | grep '2\.4'
/usr/src/jolan/linux-2.4.20/include/linux/iobuf.h
/usr/src/linux-2.4.20-tcore-akpm-preempt/include/linux/iobuf.h
/usr/src/linux-2.4.18-tcore-perfctr/include/linux/iobuf.h
/usr/src/linux-2.4.20-plain/include/linux/iobuf.h
/usr/src/linux-2.4.20-skas3/include/linux/iobuf.h
/usr/src/linux-2.5.69>tar tjf ../kernel/linux-2.5.69.tar.bz2 | grep 'iobuf\.h'
/usr/src/linux-2.5.69>
/usr/src/linux-2.5.69>tar tvjf ../kernel/linux-2.5.69.tar.bz2 | grep 'blkmtd\.c'
-rw-r--r-- torvalds/torvalds 36273 2003-05-05 01:52:59 linux-2.5.69/drivers/mtd/devices/blkmtd.c
/usr/src/linux-2.5.69>ls -l drivers/mtd/devices/blkmtd.c
-rw-r--r-- 1 carlo carlo 36273 May 5 01:52 drivers/mtd/devices/blkmtd.c
/usr/src/linux-2.5.69>bzcat ../kernel/patch-2.5.70.bz2 | grep blkmtd
/usr/src/linux-2.5.69>
--
Carlo Wood <carlo@alinoe.com>
reply other threads:[~2003-06-06 12:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030606130747.GA9861@alinoe.com \
--to=carlo@alinoe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spse@secret.org.uk \
/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