linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Weston Andros Adamson <dros@netapp.com>
Subject: linux-next: build warning after merge of the nfs tree
Date: Tue, 20 Mar 2012 13:14:27 +1100	[thread overview]
Message-ID: <20120320131427.b166ba88d4ea86cea3ec8d7f@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 565 bytes --]

Hi Trond,

After merging the nfs tree, today's linux-next build (powerpc
ppc64_defconfig) produced lots of this warning:

include/linux/nfs_fs.h: In function 'nfs_display_fhandle_hash':
include/linux/nfs_fs.h:416:1: warning: no return statement in function returning non-void [-Wreturn-type]

Introduced by commit d8e0539ebdff ("NFS: add filehandle crc for debug
display").  But made obvious by commit 855fa894a2b2 ("SUNRPC/NFS: Add
Kbuild dependencies for NFS_DEBUG/RPC_DEBUG").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2012-03-20  2:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20  2:14 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-08-07  0:36 linux-next: build warning after merge of the nfs tree Stephen Rothwell
2020-08-11 23:10 ` Stephen Rothwell
2018-06-05  0:17 Stephen Rothwell
2018-06-05 14:53 ` Trond Myklebust
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
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=20120320131427.b166ba88d4ea86cea3ec8d7f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dros@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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).