All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	kbuild-all@01.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs:dev-test 40/41] fs/f2fs/segment.c:1601:6: sparse: symbol 'release_discard_addr' was not declared. Should it be static?
Date: Fri, 27 Apr 2018 03:57:31 +0800	[thread overview]
Message-ID: <201804270303.VPJ9nTL4%fengguang.wu@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
head:   57ef368c8663e2198fadc0cfecdf67e0fe11e65a
commit: 6f89409e87ce2a41baa5650c978857f306c02859 [40/41] f2fs: introduce release_discard_addr() for cleanup
reproduce:
        # apt-get install sparse
        git checkout 6f89409e87ce2a41baa5650c978857f306c02859
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

   fs/f2fs/segment.c:1052:26: sparse: expression using sizeof(void)
   fs/f2fs/segment.c:1052:26: sparse: expression using sizeof(void)
>> fs/f2fs/segment.c:1601:6: sparse: symbol 'release_discard_addr' was not declared. Should it be static?
   fs/f2fs/segment.c:2420:27: sparse: expression using sizeof(void)
   fs/f2fs/segment.h:373:28: sparse: expression using sizeof(void)
   fs/f2fs/segment.h:373:28: sparse: expression using sizeof(void)
   fs/f2fs/segment.c:3368:36: sparse: expression using sizeof(void)
   fs/f2fs/segment.c:3368:36: sparse: expression using sizeof(void)

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

             reply	other threads:[~2018-04-26 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 19:57 kbuild test robot [this message]
2018-04-26 19:57 ` [RFC PATCH f2fs] f2fs: release_discard_addr() can be static kbuild test robot
2018-04-27  2:38   ` Chao Yu

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=201804270303.VPJ9nTL4%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=yuchao0@huawei.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.