linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: List Linux Next Mailing <linux-next@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Fred A Isaman IV <fred.isaman@gmail.com>
Subject: Re: linux-next: build warning after merge of the nfs tree
Date: Tue, 5 Jun 2018 10:53:44 -0400	[thread overview]
Message-ID: <CAABAsM4sBJukct3Ah7L7h2vg1dxzLWiVsSthk6ZECm3Guem4Pg@mail.gmail.com> (raw)
Message-ID: <20180605145344.6fUEO4IeQAhxWT6IRj7HjS6DF3Fzdrarun7BhUAGxNY@z> (raw)
In-Reply-To: <20180605101741.658efe5f@canb.auug.org.au>

On Mon, 4 Jun 2018 at 20:18, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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

Thanks Stephen! I've appended a fix to the linux-next branch.

Cheers
 Trond

  reply	other threads:[~2018-06-05 14:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05  0:17 linux-next: build warning after merge of the nfs tree Stephen Rothwell
2018-06-05 14:53 ` Trond Myklebust [this message]
2018-06-05 14:53   ` 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=CAABAsM4sBJukct3Ah7L7h2vg1dxzLWiVsSthk6ZECm3Guem4Pg@mail.gmail.com \
    --to=trondmy@gmail.com \
    --cc=fred.isaman@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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).