From: kernel test robot <lkp@intel.com>
To: Reji Thomas <rejithomas@juniper.net>, kuba@kernel.org
Cc: kbuild-all@lists.01.org, david.lebrun@uclouvain.be,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, rejithomas@juniper.net,
rejithomas.d@gmail.com
Subject: Re: [PATCH] IPv6: sr: Fix End.X nexthop to use oif.
Date: Wed, 14 Oct 2020 00:11:52 +0800 [thread overview]
Message-ID: <202010140034.DsJp5E6w-lkp@intel.com> (raw)
In-Reply-To: <20201013120151.9777-1-rejithomas@juniper.net>
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
Hi Reji,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.9 next-20201013]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Reji-Thomas/IPv6-sr-Fix-End-X-nexthop-to-use-oif/20201013-204935
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 865c50e1d279671728c2936cb7680eb89355eeea
config: x86_64-randconfig-s022-20201013 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-rc1-dirty
# https://github.com/0day-ci/linux/commit/8d40085b9b014197ce7a7e8927730796bf50adb0
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Reji-Thomas/IPv6-sr-Fix-End-X-nexthop-to-use-oif/20201013-204935
git checkout 8d40085b9b014197ce7a7e8927730796bf50adb0
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
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/ipv6/seg6_local.c:222:5: sparse: sparse: symbol 'seg6_strict_lookup_nexthop' 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: 31628 bytes --]
next prev parent reply other threads:[~2020-10-13 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 12:01 [PATCH] IPv6: sr: Fix End.X nexthop to use oif Reji Thomas
2020-10-13 16:11 ` kernel test robot [this message]
2020-10-13 16:11 ` [RFC PATCH] IPv6: sr: seg6_strict_lookup_nexthop() can be static kernel test robot
2020-10-13 17:01 ` [PATCH] IPv6: sr: Fix End.X nexthop to use oif Jakub Kicinski
2020-10-14 18:34 ` kernel 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=202010140034.DsJp5E6w-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=david.lebrun@uclouvain.be \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rejithomas.d@gmail.com \
--cc=rejithomas@juniper.net \
/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