netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hoang Huu Le <hoang.h.le@dektech.com.au>,
	jmaloy@redhat.com, maloy@donjonn.com, ying.xue@windriver.com,
	tipc-discussion@lists.sourceforge.net, netdev@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [net-next] tipc: update a binding service via broadcast
Date: Sun, 7 Jun 2020 16:18:13 +0800	[thread overview]
Message-ID: <202006071653.ii65Aozn%lkp@intel.com> (raw)
In-Reply-To: <20200607042443.11104-1-hoang.h.le@dektech.com.au>

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

Hi Hoang,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on net-next/master]
[also build test WARNING on linus/master next-20200605]
[cannot apply to v5.7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Hoang-Huu-Le/tipc-update-a-binding-service-via-broadcast/20200607-122712
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git cb8e59cc87201af93dfbb6c3dccc8fcad72a09c2
config: i386-randconfig-s002-20200607 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-247-gcadbd124-dirty
        # save the attached .config to linux build tree
        make W=1 C=1 ARCH=i386 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> net/tipc/name_distr.c:323:16: sparse: sparse: symbol 'tipc_named_dequeue' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37946 bytes --]

  parent reply	other threads:[~2020-06-07  8:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07  4:24 [net-next] tipc: update a binding service via broadcast Hoang Huu Le
2020-06-07  5:38 ` kernel test robot
2020-06-07  6:22 ` kernel test robot
2020-06-07  8:18 ` kernel test robot [this message]
2020-06-07  8:18 ` [RFC PATCH] tipc: tipc_named_dequeue() can be static kernel test robot
2020-06-07 19:03 ` [net-next] tipc: update a binding service via broadcast Jon Maloy
2020-06-07 23:56 ` David Miller

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=202006071653.ii65Aozn%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hoang.h.le@dektech.com.au \
    --cc=jmaloy@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=maloy@donjonn.com \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=ying.xue@windriver.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 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).