From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
"J. Bruce Fields" <bfields@fieldses.org>,
Jeff Layton <jlayton@poochiereds.net>
Subject: Re: linux-next: Tree for Mar 8 (nfsd)
Date: Tue, 8 Mar 2016 08:55:29 -0800 [thread overview]
Message-ID: <56DF0401.6010901@infradead.org> (raw)
In-Reply-To: <20160308165122.68ececf7@canb.auug.org.au>
On 03/07/16 21:51, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160307:
>
on x86_64:
when CONFIG_BLOCK is not enabled:
../fs/nfsd/nfs4layouts.c: In function 'nfsd4_setup_layout_type':
../fs/nfsd/nfs4layouts.c:145:39: error: dereferencing pointer to incomplete type
sb->s_bdev && sb->s_bdev->bd_disk->fops->pr_ops)
^
--
~Randy
next parent reply other threads:[~2016-03-08 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160308165122.68ececf7@canb.auug.org.au>
2016-03-08 16:55 ` Randy Dunlap [this message]
2016-03-08 17:02 ` linux-next: Tree for Mar 8 (nfsd) Christoph Hellwig
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=56DF0401.6010901@infradead.org \
--to=rdunlap@infradead.org \
--cc=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).