From: Xiaoji Liu <xiaoji14@yahoo.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1: kernel image compile ok, but modules compile failed
Date: Tue, 22 Jul 2003 12:25:19 -0700 (PDT) [thread overview]
Message-ID: <20030722192519.35904.qmail@web41903.mail.yahoo.com> (raw)
In-Reply-To: <20030722191241.GA2003@mars.ravnborg.org>
--- Sam Ravnborg <sam@ravnborg.org> wrote:
> On Tue, Jul 22, 2003 at 11:48:42AM -0700, Xiaoji Liu
> wrote:
> > Hello,
> >
> > when i compile kernel 2.6.0-test1
> > It gave 'parse error' message when compiling file
> > drivers/mtd/devices/blkmtd.c
> > (around line 700)
> >
> > I opened the source file and saw this:
> >
> > static int blkmtd_write(struct mtd_info *mtd,
> loff_t
> > to, size_t len,
> > size_t *retlen, const u_char *buf)
> > {
> > mtd_raw_dev_data_t *rawdevice = mtd->priv;
> > int err = 0;
> > int offset;
> > int pagenr;
> > size_t len1 = 0, len2 = 0, len3 = 0;
> > struct page **pages;
> > int pagecnt = 0;
> > char b[BDEVNAME_SIZE];
> > 21 e3
> > *retlen = 0;
>
> They where added by Andrew by accident, and can
> safely be deleted.
> It was part of the "[PATCH] make the bdevname() API
> sane"
> that involved several files.
>
> Sam
are there any other such problems around? :)
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
prev parent reply other threads:[~2003-07-22 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 18:48 2.6.0-test1: kernel image compile ok, but modules compile failed Xiaoji Liu
2003-07-22 19:12 ` Sam Ravnborg
2003-07-22 19:25 ` Xiaoji Liu [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=20030722192519.35904.qmail@web41903.mail.yahoo.com \
--to=xiaoji14@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).