From: kbuild test robot <lkp@intel.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: [net-next:master 1066/1074] include/net/page_pool.h:165:1: warning: no return statement in function returning non-void
Date: Thu, 20 Jun 2019 04:35:39 +0800 [thread overview]
Message-ID: <201906200438.pHY3J908%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: 6c9bef32c6e742e847fc28c9bf7721cbfa003fa6
commit: 99c07c43c4ea0bc101331401a0fabfc51933c6a3 [1066/1074] xdp: tracking page_pool resources and safe removal
config: xtensa-common_defconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 99c07c43c4ea0bc101331401a0fabfc51933c6a3
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=xtensa
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from net//core/xdp.c:14:0:
include/net/page_pool.h: In function 'page_pool_request_shutdown':
>> include/net/page_pool.h:165:1: warning: no return statement in function returning non-void [-Wreturn-type]
}
^
vim +165 include/net/page_pool.h
148
149 /* API user MUST have disconnected alloc-side (not allowed to call
150 * page_pool_alloc_pages()) before calling this. The free-side can
151 * still run concurrently, to handle in-flight packet-pages.
152 *
153 * A request to shutdown can fail (with false) if there are still
154 * in-flight packet-pages.
155 */
156 bool __page_pool_request_shutdown(struct page_pool *pool);
157 static inline bool page_pool_request_shutdown(struct page_pool *pool)
158 {
159 /* When page_pool isn't compiled-in, net/core/xdp.c doesn't
160 * allow registering MEM_TYPE_PAGE_POOL, but shield linker.
161 */
162 #ifdef CONFIG_PAGE_POOL
163 return __page_pool_request_shutdown(pool);
164 #endif
> 165 }
166
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 10378 bytes --]
reply other threads:[~2019-06-19 20:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201906200438.pHY3J908%lkp@intel.com \
--to=lkp@intel.com \
--cc=brouer@redhat.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
/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).