All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: linux-kernel@vger.kernel.org, kbuild-all@01.org,
	Ashish Sangwan <a.sangwan@samsung.com>,
	xfs@oss.sgi.com
Subject: [PATCH dgc-xfs] xfs: xfs_shift_file_space can be static
Date: Wed, 25 Mar 2015 15:42:08 +0800	[thread overview]
Message-ID: <20150325074208.GA22854@snb> (raw)
In-Reply-To: <201503251558.Dje24s0l%fengguang.wu@intel.com>


Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
 xfs_bmap_util.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c
index fe1f11b..e867573 100644
--- a/fs/xfs/xfs_bmap_util.c
+++ b/fs/xfs/xfs_bmap_util.c
@@ -1383,7 +1383,7 @@ out:
  * If we are shifting right, we will start with last extent inside file space
  * and continue until we reach the block corresponding to offset.
  */
-int
+static int
 xfs_shift_file_space(
 	struct xfs_inode        *ip,
 	xfs_off_t               offset,

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <fengguang.wu@intel.com>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: kbuild-all@01.org, Dave Chinner <david@fromorbit.com>,
	Ashish Sangwan <a.sangwan@samsung.com>,
	xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: [PATCH dgc-xfs] xfs: xfs_shift_file_space can be static
Date: Wed, 25 Mar 2015 15:42:08 +0800	[thread overview]
Message-ID: <20150325074208.GA22854@snb> (raw)
In-Reply-To: <201503251558.Dje24s0l%fengguang.wu@intel.com>


Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
 xfs_bmap_util.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c
index fe1f11b..e867573 100644
--- a/fs/xfs/xfs_bmap_util.c
+++ b/fs/xfs/xfs_bmap_util.c
@@ -1383,7 +1383,7 @@ out:
  * If we are shifting right, we will start with last extent inside file space
  * and continue until we reach the block corresponding to offset.
  */
-int
+static int
 xfs_shift_file_space(
 	struct xfs_inode        *ip,
 	xfs_off_t               offset,

  reply	other threads:[~2015-03-25  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  7:42 [dgc-xfs:fallocate-insert-range 10/10] fs/xfs/xfs_bmap_util.c:1387:1: sparse: symbol 'xfs_shift_file_space' was not declared. Should it be static? kbuild test robot
2015-03-25  7:42 ` kbuild test robot
2015-03-25  7:42 ` kbuild test robot [this message]
2015-03-25  7:42   ` [PATCH dgc-xfs] xfs: xfs_shift_file_space can be static kbuild test robot

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=20150325074208.GA22854@snb \
    --to=fengguang.wu@intel.com \
    --cc=a.sangwan@samsung.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=xfs@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.