linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: "Rees, James" <rees@umich.edu>
Cc: NFS list <linux-nfs@vger.kernel.org>,
	Fred Isaman <iisaman@netapp.com>,
	Andy Adamson <andros@netapp.com>
Subject: pnfs block build errors in 2.6.38
Date: Mon, 17 Jan 2011 19:31:11 +0200	[thread overview]
Message-ID: <4D347CDF.2080600@panasas.com> (raw)

Jim, I get the following build errors in 2.6.38:

/usr0/export/dev/bhalevy/git/linux-pnfs-bh-nfs41/fs/nfs/blocklayout/blocklayoutdev.c: In function 'nfs4_blkdev_get':
/usr0/export/dev/bhalevy/git/linux-pnfs-bh-nfs41/fs/nfs/blocklayout/blocklayoutdev.c:58: error: implicit declaration of function 'open_by_devnum'
/usr0/export/dev/bhalevy/git/linux-pnfs-bh-nfs41/fs/nfs/blocklayout/blocklayoutdev.c:58: warning: assignment makes pointer from integer without a cast
/usr0/export/dev/bhalevy/git/linux-pnfs-bh-nfs41/fs/nfs/blocklayout/blocklayoutdev.c: In function 'nfs4_blkdev_put':
/usr0/export/dev/bhalevy/git/linux-pnfs-bh-nfs41/fs/nfs/blocklayout/blocklayoutdev.c:75: error: implicit declaration of function 'bd_release'

I pushed the tree to git://git.bhalevy.com/linux-pnfs.git

Mind taking a look at this?

Andy, Fred: you can synchronize with this tree at this point, after the rebase on top
of Bruce's latest changes it won't change much, so feel free to go for it :)

Thanks,

Benny

             reply	other threads:[~2011-01-17 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 17:31 Benny Halevy [this message]
2011-01-17 17:57 ` pnfs block build errors in 2.6.38 Fred Isaman
2011-01-17 19:03 ` Jim Rees

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=4D347CDF.2080600@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=andros@netapp.com \
    --cc=iisaman@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@umich.edu \
    /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;
as well as URLs for NNTP newsgroup(s).