From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Greg KH <greg@kroah.com>, "Randy.Dunlap" <rddunlap@osdl.org>
Subject: Re: 2.5.68-bk10 blkmtd.c:219: warning: implicit declaration of function `alloc_kiovec'
Date: 01 May 2003 00:58:39 +0100 [thread overview]
Message-ID: <1051747119.5315.28.camel@flat41> (raw)
In-Reply-To: <1051745126.5274.22.camel@flat41>
On Thu, 2003-05-01 at 00:25, Grzegorz Jaskiewicz wrote:
> Well, "burned" on ieee1394 i will not try to patch it my self :)
> Anyway, i can live without those drivers :)
> drivers/mtd/devices/blkmtd.c:52:25: linux/iobuf.h: No such file or
> directory
I've tried to investigate this. What happend to iobuf.{ch} ?
I guess bit more changes are required to make it running before 2.6 :)
Btw, authors email in head of blkmtd.c is bad.
Fanny thing, after removing this include there is declaration :
/* readpage() - reads one page from the block device */
static int blkmtd_readpage(mtd_raw_dev_data_t *rawdevice, struct page *page)
{
int err;
int sectornr, sectors, i;
struct kiobuf *iobuf;
^^^^^^^
unsigned long *blocks;
Fast fgrep in kernel sources gives me no answer about this structure declaration.
any help guys ?
--
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 labs
next prev parent reply other threads:[~2003-04-30 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 23:25 2.5.68-bk10 blkmtd.c:219: warning: implicit declaration of function `alloc_kiovec' Grzegorz Jaskiewicz
2003-04-30 23:58 ` Grzegorz Jaskiewicz [this message]
2003-05-01 0:10 ` Andrew Morton
2003-05-01 0:32 ` Grzegorz Jaskiewicz
2003-05-01 0:35 ` Andrew Morton
2003-05-01 9:01 ` 2.5.68-bk10 blkmtd.c:219: warning: implicit declaration offunction `alloc_kiovec' Adrian Bunk
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=1051747119.5315.28.camel@flat41 \
--to=gj@pointblue.com.pl \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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.