linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"rdunlap@infradead.org" <rdunlap@infradead.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>
Subject: Re: linux-next: Tree for May 15 (nfs/fsinfo.c)
Date: Fri, 15 May 2020 16:32:49 +0000	[thread overview]
Message-ID: <ef6274c2de9fcc2e1820db1ac8f0b7602a9fe6b0.camel@hammerspace.com> (raw)
In-Reply-To: <129e8dee-76c3-ba9d-e692-d145653bbaaa@infradead.org>

Hi Randy,

On Fri, 2020-05-15 at 08:28 -0700, Randy Dunlap wrote:
> On 5/15/20 5:42 AM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20200514:
> > 
> > -----------------------------------------------------------------
> > -----------
> 
> on i386:
> 
>   CC      fs/nfs/fsinfo.o
> ../fs/nfs/fsinfo.c: In function ‘nfs_fsinfo_get_supports’:
> ../fs/nfs/fsinfo.c:153:12: error: ‘const struct nfs_server’ has no
> member named ‘attr_bitmask’
>   if (server->attr_bitmask[0] & FATTR4_WORD0_SIZE)
>             ^~
> ../fs/nfs/fsinfo.c:155:12: error: ‘const struct nfs_server’ has no
> member named ‘attr_bitmask’
>   if (server->attr_bitmask[1] & FATTR4_WORD1_NUMLINKS)
>             ^~
> ../fs/nfs/fsinfo.c:158:12: error: ‘const struct nfs_server’ has no
> member named ‘attr_bitmask’
>   if (server->attr_bitmask[0] & FATTR4_WORD0_ARCHIVE)
>             ^~
> ../fs/nfs/fsinfo.c:160:12: error: ‘const struct nfs_server’ has no
> member named ‘attr_bitmask’
>   if (server->attr_bitmask[0] & FATTR4_WORD0_HIDDEN)
>             ^~
> ../fs/nfs/fsinfo.c:162:12: error: ‘const struct nfs_server’ has no
> member named ‘attr_bitmask’
>   if (server->attr_bitmask[1] & FATTR4_WORD1_SYSTEM)
>             ^~
> ../fs/nfs/fsinfo.c: In function ‘nfs_fsinfo_get_features’:
> ../fs/nfs/fsinfo.c:205:12: error: ‘const struct nfs_server’ has no
> member named ‘attr_bitmask’
>   if (server->attr_bitmask[0] & FATTR4_WORD0_CASE_INSENSITIVE)
>             ^~
> ../fs/nfs/fsinfo.c:207:13: error: ‘const struct nfs_server’ has no
> member named ‘attr_bitmask’
>   if ((server->attr_bitmask[0] & FATTR4_WORD0_ARCHIVE) ||
>              ^~
> ../fs/nfs/fsinfo.c:208:13: error: ‘const struct nfs_server’ has no
> member named ‘attr_bitmask’
>       (server->attr_bitmask[0] & FATTR4_WORD0_HIDDEN) ||
>              ^~
> ../fs/nfs/fsinfo.c:209:13: error: ‘const struct nfs_server’ has no
> member named ‘attr_bitmask’
>       (server->attr_bitmask[1] & FATTR4_WORD1_SYSTEM))
>              ^~
> 
> Full randconfig file is attached.
> 

Where is this file coming from? I'm not aware of any fs/nfs/fsinfo.c in
the current tree or in my linux-next for 5.7, and a cursory glance is
showing it up in Anna's linux-next for the 5.8 merge window.

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2020-05-15 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 12:42 linux-next: Tree for May 15 Stephen Rothwell
2020-05-15 15:28 ` linux-next: Tree for May 15 (nfs/fsinfo.c) Randy Dunlap
2020-05-15 16:32   ` Trond Myklebust [this message]
2020-05-15 16:33     ` Trond Myklebust
2020-05-15 16:35     ` 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=ef6274c2de9fcc2e1820db1ac8f0b7602a9fe6b0.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rdunlap@infradead.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).