From: Wayne.Brown@altec.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
marpet@buy.pl (Marek Pętlicki),
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.4-ac7
Date: Fri, 11 May 2001 14:03:50 -0500 [thread overview]
Message-ID: <86256A49.0068AF0B.00@smtpnotes.altec.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 233 bytes --]
My modules/filemap.ver has the same in it as yours.
Wayne
Alan Cox <alan@lxorguk.ukuu.org.uk> on 05/11/2001 01:52:18 PM
To: Wayne Brown/Corporate/Altec@Altec
cc: alan@lxorguk.ukuu.org.uk (Alan Cox), marpet@buy.pl (Marek P
[-- Attachment #2: Type: text/plain, Size: 86 bytes --]
ętlicki),
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.4-ac7
[-- Attachment #3: Type: text/plain, Size: 519 bytes --]
> I always make mrproper after applying your patches, and I still got exactly
the
> same problem with nfs that Marek found. There were no errors or warnings
during
> the compile of the objects in the fs/nfs directory or the linking of nfs.o.
>
Curious : my build has
#define __ver_filemap_fdatasync f18ce7a1
#define filemap_fdatasync _set_ver(filemap_fdatasync)
#define __ver_filemap_fdatawait d4250148
#define filemap_fdatawait _set_ver(filemap_fdatawait)
in modules/filemap.ver
I'll have a look
next reply other threads:[~2001-05-11 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 19:03 Wayne.Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-11 18:50 Linux 2.4.4-ac7 Wayne.Brown
2001-05-11 18:52 ` Alan Cox
2001-05-11 13:53 Alan Cox
2001-05-11 17:36 ` Marek Pętlicki
2001-05-11 17:53 ` Alan Cox
2001-05-11 19:56 ` Danny ter Haar
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=86256A49.0068AF0B.00@smtpnotes.altec.com \
--to=wayne.brown@altec.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marpet@buy.pl \
/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.