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>
Subject: Re: linux-next: Tree for Feb 13 (nfsd)
Date: Fri, 13 Feb 2015 10:18:42 -0800 [thread overview]
Message-ID: <54DE4002.6050805@infradead.org> (raw)
In-Reply-To: <20150213165615.1ad43047@canb.auug.org.au>
On 02/12/15 21:56, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150212:
on x86_64, when
# CONFIG_NFS_FS is not set
CONFIG_NFSD=y
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_V4 is not set
In file included from ../include/linux/linkage.h:4:0,
from ../include/linux/preempt.h:9,
from ../include/linux/spinlock.h:50,
from ../include/linux/mmzone.h:7,
from ../include/linux/gfp.h:5,
from ../include/linux/slab.h:14,
from ../fs/nfsd/nfsctl.c:7:
../fs/nfsd/xdr4.h: In function 'set_change_info':
../fs/nfsd/xdr4.h:633:13: error: 'struct svc_fh' has no member named 'fh_pre_saved'
BUG_ON(!fhp->fh_pre_saved);
^
../include/linux/compiler.h:164:42: note: in definition of macro 'unlikely'
# define unlikely(x) __builtin_expect(!!(x), 0)
^
../fs/nfsd/xdr4.h:633:2: note: in expansion of macro 'BUG_ON'
BUG_ON(!fhp->fh_pre_saved);
^
In file included from ../fs/nfsd/pnfs.h:8:0,
from ../fs/nfsd/nfsctl.c:24:
../fs/nfsd/xdr4.h:634:21: error: 'struct svc_fh' has no member named 'fh_post_saved'
cinfo->atomic = fhp->fh_post_saved;
^
../fs/nfsd/xdr4.h:637:28: error: 'struct svc_fh' has no member named 'fh_pre_change'
cinfo->before_change = fhp->fh_pre_change;
^
../fs/nfsd/xdr4.h:638:27: error: 'struct svc_fh' has no member named 'fh_post_change'
cinfo->after_change = fhp->fh_post_change;
^
../fs/nfsd/xdr4.h:639:31: error: 'struct svc_fh' has no member named 'fh_pre_ctime'
cinfo->before_ctime_sec = fhp->fh_pre_ctime.tv_sec;
^
../fs/nfsd/xdr4.h:640:32: error: 'struct svc_fh' has no member named 'fh_pre_ctime'
cinfo->before_ctime_nsec = fhp->fh_pre_ctime.tv_nsec;
^
../fs/nfsd/xdr4.h:641:30: error: 'struct svc_fh' has no member named 'fh_post_attr'
cinfo->after_ctime_sec = fhp->fh_post_attr.ctime.tv_sec;
^
../fs/nfsd/xdr4.h:642:31: error: 'struct svc_fh' has no member named 'fh_post_attr'
cinfo->after_ctime_nsec = fhp->fh_post_attr.ctime.tv_nsec;
^
--
~Randy
next prev parent reply other threads:[~2015-02-13 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 5:56 linux-next: Tree for Feb 13 Stephen Rothwell
2015-02-13 11:03 ` Sabrina Dubroca
2015-02-13 18:18 ` Randy Dunlap [this message]
2015-02-13 18:54 ` linux-next: Tree for Feb 13 (runtime failures and 'non-zero nr_pmds' messages) Guenter Roeck
2015-02-13 23:37 ` Stephen Rothwell
2015-02-14 4:45 ` Guenter Roeck
[not found] ` <20150213165615.1ad43047-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2015-02-14 0:32 ` linux-next: Tree for Feb 13 (iio/magnetometer/ak8975.c) Randy Dunlap
2015-02-14 0:34 ` Randy Dunlap
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=54DE4002.6050805@infradead.org \
--to=rdunlap@infradead.org \
--cc=bfields@fieldses.org \
--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).