public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Dyson <will_dyson@pobox.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test5-mm4: BeFS compile error
Date: Mon, 22 Sep 2003 13:57:13 -0400	[thread overview]
Message-ID: <1064253433.346.11.camel@thalience> (raw)
In-Reply-To: <20030922114958.GR6325@fs.tum.de>

On Mon, 2003-09-22 at 07:49, Adrian Bunk wrote:
> On Mon, Sep 22, 2003 at 01:35:48AM -0700, Andrew Morton wrote:
> >...
> > befs-use-parser.patch
> >   BEFS: Use table-driven option parsing
> >...
> 
> It seems this patch broke the compilation of BeFS:
> 
> <--  snip  -->
> 
> ...
>   CC      fs/befs/linuxvfs.o
> fs/befs/linuxvfs.c: In function `parse_options':
> fs/befs/linuxvfs.c:712: too few arguments to function `match_int'
> fs/befs/linuxvfs.c:724: too few arguments to function `match_int'
> make[2]: *** [fs/befs/linuxvfs.o] Error 1

Seems Andrew merged a different version of the options patch than the
one that was posted to the list. I can make a fixup tonight.

Also, from looking at the test5-mm4 patch, I think that match_number()
from lib/parser.c is ignoring the base argument and using a hardcoded
value of zero for the simple_strtol() call. This should result in
match_octal() and match_hex() being broken (well, being the same as
match_int).

-- 
Will Dyson
"Back off man, I'm a scientist!" -Dr. Peter Venkman


  reply	other threads:[~2003-09-22 17:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22  8:35 2.6.0-test5-mm4 Andrew Morton
2003-09-22 11:49 ` 2.6.0-test5-mm4: BeFS compile error Adrian Bunk
2003-09-22 17:57   ` Will Dyson [this message]
2003-09-22 12:09 ` 2.6.0-test5-mm4 Florian Schanda
2003-09-22 12:17 ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 13:48   ` 2.6.0-test5-mm4 viro
2003-09-22 14:29     ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 14:30   ` 2.6.0-test5-mm4 Florian Schanda
2003-09-22 14:36   ` 2.6.0-test5-mm4 Zilvinas Valinskas
2003-09-22 13:49     ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 13:54       ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 18:55     ` 2.6.0-test5-mm4 Andrew Morton
2003-09-22 21:27       ` 2.6.0-test5-mm4 Peter Osterlund
2003-09-22 21:45         ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-25  0:13           ` 2.6.0-test5-mm4 Peter Osterlund
2003-09-25 12:43             ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-22 21:44       ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-22 19:10 ` 2.6.0-test5-mm4: wanxl doesn't compile with gcc 2.95 Adrian Bunk
2003-09-22 19:22   ` Andrew Morton
2003-09-22 22:42   ` Krzysztof Halasa
2003-09-22 22:41     ` Andrew Morton
2003-09-23 13:24       ` Krzysztof Halasa
2003-09-24  9:18 ` 2.6.0-test5-mm4 boot crash Helge Hafting
2003-09-24  9:57   ` viro

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=1064253433.346.11.camel@thalience \
    --to=will_dyson@pobox.com \
    --cc=akpm@osdl.org \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.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