mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@digeo.com>, David Woodhouse <dwmw2@redhat.com>
Cc: Grzegorz Jaskiewicz <gj@pointblue.com.pl>,
	linux-kernel@vger.kernel.org, greg@kroah.com, rddunlap@osdl.org
Subject: Re: 2.5.68-bk10 blkmtd.c:219: warning: implicit declaration offunction `alloc_kiovec'
Date: Thu, 1 May 2003 11:01:31 +0200	[thread overview]
Message-ID: <20030501090131.GQ14959@fs.tum.de> (raw)
In-Reply-To: <20030430171047.2f22ed70.akpm@digeo.com>

On Wed, Apr 30, 2003 at 05:10:47PM -0700, Andrew Morton wrote:
> Grzegorz Jaskiewicz <gj@pointblue.com.pl> wrote:
> >
> >   struct kiobuf *iobuf;
> > 	^^^^^^^
> >   unsigned long *blocks;
> > 
> > Fast fgrep in kernel sources gives me no answer about this structure declaration.
> > 
> 
> blkmtd died when kiobufs were removed.  The maintainer said "oh well, OK, I
> need to rewrite it anyway" but that obviously has not yet happened.

There's a new blkmtd in the MTD CVS.

David:
What are your current plans regarding merging the MTD CVS into 2.5?

cu
Adrian

[1] http://www.linux-mtd.infradead.org/

-- 

       "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


      parent reply	other threads:[~2003-05-01  8:49 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
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     ` Adrian Bunk [this message]

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=20030501090131.GQ14959@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=akpm@digeo.com \
    --cc=dwmw2@redhat.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®