linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Howells <dhowells@redhat.com>,
	linux-afs@lists.infradead.org,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 4 (fs/afs/)
Date: Mon, 4 Jun 2018 09:12:35 -0700	[thread overview]
Message-ID: <7e4a317a-d57e-1499-dc1e-2eba35610632@infradead.org> (raw)
In-Reply-To: <20180604215911.75399f6e@canb.auug.org.au>

On 06/04/2018 04:59 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20180601:
> 

on x86_64:

# CONFIG_PROC_FS is not set


../fs/afs/proc.c: In function �afs_proc_init�:
../fs/afs/proc.c:604:2: error: implicit declaration of function �proc_create_net_data_write� [-Werror=implicit-function-declaration]
  if (!proc_create_net_data_write("cells", 0644, p,
  ^
../fs/afs/proc.c:609:6: error: implicit declaration of function �proc_create_net_single_write� [-Werror=implicit-function-declaration]
      !proc_create_net_single_write("rootcell", 0644, p,
      ^
../fs/afs/proc.c: At top level:
../fs/afs/proc.c:517:12: warning: �afs_proc_stats_show� defined but not used [-Wunused-function]
 static int afs_proc_stats_show(struct seq_file *m, void *v)
            ^
cc1: some warnings being treated as errors
../scripts/Makefile.build:311: recipe for target 'fs/afs/proc.o' failed


afs seems not to handle CONFIG_PROC_FS=n at all.

-- 
~Randy

       reply	other threads:[~2018-06-04 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180604215911.75399f6e@canb.auug.org.au>
2018-06-04 16:12 ` Randy Dunlap [this message]
2018-06-14 15:08 ` David Howells

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=7e4a317a-d57e-1499-dc1e-2eba35610632@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: linux-next: Tree for Jun 4 (fs/afs/)' \
    /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

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).