From: Nick Piggin <npiggin@suse.de>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: Linux Filesystems <linux-fsdevel@vger.kernel.org>,
Mark Fasheh <mark.fasheh@oracle.com>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: 2.6.21-rc6 new aops patchset
Date: Fri, 13 Apr 2007 01:25:25 +0200 [thread overview]
Message-ID: <20070412232525.GA23523@wotan.suse.de> (raw)
In-Reply-To: <1176395857.24509.137.camel@dyn9047017100.beaverton.ibm.com>
On Thu, Apr 12, 2007 at 09:37:36AM -0700, Badari Pulavarty wrote:
> On Thu, 2007-04-12 at 06:48 +0200, Nick Piggin wrote:
> > http://www.kernel.org/pub/linux/kernel/people/npiggin/patches/new-aops/
> >
> > 2.6.21-rc6-new-aops*
> >
> > New aops patchset against 2.6.21-rc6.
>
>
> Building modules, stage 2.
> MODPOST 558 modules
> WARNING: ".cont_prepare_write" [fs/hfsplus/hfsplus.ko] undefined!
> WARNING: ".iov_iter_advance" [fs/fuse/fuse.ko] undefined!
> WARNING: ".iov_iter_copy_from_user_atomic" [fs/fuse/fuse.ko] undefined!
> WARNING: ".iov_iter_fault_in_readable" [fs/fuse/fuse.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
Grr, thanks. I guess I should be doing allmodconfig as well :P
I'll add the exports.
next prev parent reply other threads:[~2007-04-12 23:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 4:48 2.6.21-rc6 new aops patchset Nick Piggin
2007-04-12 16:37 ` Badari Pulavarty
2007-04-12 23:25 ` Nick Piggin [this message]
2007-04-13 16:42 ` Badari Pulavarty
2007-04-14 0:52 ` Nick Piggin
2007-04-17 18:41 ` Badari Pulavarty
2007-04-18 5:04 ` Nick Piggin
2007-04-12 17:05 ` Miklos Szeredi
2007-04-12 23:41 ` Nick Piggin
2007-04-12 17:27 ` Mark Fasheh
2007-04-12 23:45 ` Nick Piggin
2007-04-17 0:19 ` Mark Fasheh
2007-04-17 5:59 ` Nick Piggin
2007-04-17 9:33 ` Christoph Hellwig
2007-04-17 9:47 ` Nick Piggin
2007-04-17 9:58 ` Christoph Hellwig
2007-04-17 11:18 ` Nick Piggin
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=20070412232525.GA23523@wotan.suse.de \
--to=npiggin@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=miklos@szeredi.hu \
--cc=pbadari@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox