Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Benny Halevy <bhalevy@panasas.com>
Cc: subrata@linux.vnet.ibm.com, NFS list <linux-nfs@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next <linux-next@vger.kernel.org>,
	sachinp <sachinp@linux.vnet.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Alexander Beregalov <a.beregalov@gmail.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [BUILD FAILURE 03/04] Next April 21 : x86_64 randconfig [fs/nfs/nfs.ko]
Date: Tue, 21 Apr 2009 13:49:32 -0400	[thread overview]
Message-ID: <1240336172.20441.0.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <49EE056C.1060605@panasas.com>

On Tue, 2009-04-21 at 20:42 +0300, Benny Halevy wrote:
> On Apr. 21, 2009, 19:51 +0300, Subrata Modak <subrata@linux.vnet.ibm.com> wrote:
> > I think i am observing this for the first time in any randconfig builds:
> > 
> > BUILD   arch/x86/boot/bzImage
> > Root device is (8, 3)
> > Setup is 13020 bytes (padded to 13312 bytes).
> > System is 5625 kB
> > CRC a80d60ee
> > Kernel: arch/x86/boot/bzImage is ready  (#1)
> >   Building modules, stage 2.
> >   MODPOST 514 modules
> > ERROR: "find_last_bit" [fs/nfs/nfs.ko] undefined!
> > make[1]: *** [__modpost] Error 1
> > make: *** [modules] Error 2
> > ---
> > 
> > Regards--
> > Subrata
> > 
> 
> Trond, can you please merge
> http://git.linux-nfs.org/?p=bhalevy/linux-pnfs.git;a=commitdiff;h=9f32944d1bca79038ef3e9c9a27f11803d093d8e
> into your nfsv41 and linux-next branches?
> 
> I've placed it right before "nfs41: free slot"
> in git://git.linux-nfs.org/projects/bhalevy/linux-pnfs.git nfs41-for-2.6.31
> 
> (see also this thread:
> http://article.gmane.org/gmane.linux.kernel.next/6951)

Could we just push that straight into the kernel? It seems like a
no-brainer...

Cheers
  Trond

  reply	other threads:[~2009-04-21 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 16:51 [BUILD FAILURE 03/04] Next April 21 : x86_64 randconfig [fs/nfs/nfs.ko] Subrata Modak
2009-04-21 17:42 ` Benny Halevy
2009-04-21 17:49   ` Trond Myklebust [this message]
     [not found]     ` <1240336172.20441.0.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-21 20:44       ` Benny Halevy

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=1240336172.20441.0.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=a.beregalov@gmail.com \
    --cc=bhalevy@panasas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sachinp@linux.vnet.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=subrata@linux.vnet.ibm.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