From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Trond Myklebust <trondmy@gmail•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Fred Isaman <fred.isaman@gmail•com>
Subject: linux-next: build warning after merge of the nfs tree
Date: Tue, 5 Jun 2018 10:17:41 +1000 [thread overview]
Message-ID: <20180605101741.658efe5f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
Hi Trond,
After merging the nfs tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
fs/nfs/nfs4proc.c:910:13: warning: 'nfs4_layoutget_release' defined but not used [-Wunused-function]
static void nfs4_layoutget_release(void *calldata)
^~~~~~~~~~~~~~~~~~~~~~
Introduced by commit
30ae2412e90f ("pnfs: Fix manipulation of NFS_LAYOUT_FIRST_LAYOUTGET")
in combination with
2409a976a299 ("pnfs: Add LAYOUTGET to OPEN of a new file")
# CONFIG_NFS_V4_1 is not set
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-06-05 0:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 0:17 Stephen Rothwell [this message]
2018-06-05 14:53 ` linux-next: build warning after merge of the nfs tree Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2020-08-07 0:36 Stephen Rothwell
2020-08-11 23:10 ` Stephen Rothwell
2018-01-15 21:44 Stephen Rothwell
2015-10-20 4:37 Stephen Rothwell
2014-06-17 1:26 Stephen Rothwell
2012-03-20 8:34 Stephen Rothwell
2012-03-20 13:28 ` Myklebust, Trond
2012-03-20 2:14 Stephen Rothwell
2010-08-04 1:32 Stephen Rothwell
2010-08-04 2:09 ` Trond Myklebust
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=20180605101741.658efe5f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=fred.isaman@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=trondmy@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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