From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] Re: NFS "dev_t" issues..
Date: Thu, 03 Jan 2002 16:23:37 +0100 [thread overview]
Message-ID: <3C347779.D33BD961@oracle.com> (raw)
In-Reply-To: <UTC200201030128.BAA192710.aeb@cwi.nl>
Andries.Brouwer@cwi.nl wrote:
>
> From alessandro.suardi@oracle.com Thu Jan 3 00:22:23 2002
>
> It doesn't build for me in make_rdonly() in ext3 with debug
> configured in:
>
> Yes. Still w.i.p. but a better version is now
> 2.5.2pre6-kdev_t-diff-v3 (443024 bytes).
Compiles and boots fine with my config - laptop including ext2,
ext3, fat, vfat, reiserfs, iso9660, tmpfs, ramfs, IrDA, PPP,
Xircom Cardbus (old driver), parport, floppy, ramdisk, loop,
IDE, ipv4, nfs/nfsd, samba, maestro3, usb UHCI and more. Not
everything tested and one possibly related warning:
gcc -D__KERNEL__ -I/usr/src/linux-2.5.2-pre6/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686
-DMODULE -c -o write.o write.c
write.c: In function `nfs_commit_done':
write.c:1204: warning: unsigned int format, kdev_t arg (arg 2)
Quite good so far :) thanks a lot,
--alessandro
"this machine will, will not communicate
these thoughts and the strain I am under
be a world child, form a circle before we all go under"
(Radiohead, "Street Spirit [fade out]")
next prev parent reply other threads:[~2002-01-03 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 1:28 [PATCH] Re: NFS "dev_t" issues Andries.Brouwer
2002-01-03 15:23 ` Alessandro Suardi [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-02 19:34 Andries.Brouwer
2002-01-01 22:15 Linus Torvalds
2002-01-01 22:38 ` [PATCH] " Jeff Garzik
2002-01-01 22:41 ` Linus Torvalds
2002-01-01 23:04 ` Jeff Garzik
2002-01-01 23:26 ` Linus Torvalds
2002-01-01 23:49 ` Jeff Garzik
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=3C347779.D33BD961@oracle.com \
--to=alessandro.suardi@oracle.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.