All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3 net-next 4/8] net: dsa: implement auto-normalization of MTU for bridge hardware datapath
Date: Thu, 02 Apr 2020 09:25:03 +0800	[thread overview]
Message-ID: <20200402012503.GF8179@shao2-debian> (raw)
In-Reply-To: <20200326224040.32014-5-olteanv@gmail.com>

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

Hi Vladimir,

I love your patch! Perhaps something to improve:

[auto build test WARNING on net-next/master]
[also build test WARNING on linus/master v5.6-rc7 next-20200327]
[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/Vladimir-Oltean/Configure-the-MTU-on-DSA-switches/20200327-094801
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 92b7e62e5630a370955a4760bbeb3967457034ec
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-187-gbff9b106-dirty
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
:::::: branch date: 17 hours ago
:::::: commit date: 17 hours ago

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

   net/dsa/slave.c:506:13: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected void const [noderef] <asn:3> *__vpp_verify @@    got const [noderef] <asn:3> *__vpp_verify @@
   net/dsa/slave.c:506:13: sparse:    expected void const [noderef] <asn:3> *__vpp_verify
   net/dsa/slave.c:506:13: sparse:    got struct pcpu_sw_netstats *
   net/dsa/slave.c:640:21: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected void const [noderef] <asn:3> *__vpp_verify @@    got const [noderef] <asn:3> *__vpp_verify @@
   net/dsa/slave.c:640:21: sparse:    expected void const [noderef] <asn:3> *__vpp_verify
   net/dsa/slave.c:640:21: sparse:    got struct pcpu_sw_netstats *
   net/dsa/slave.c:1106:21: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected void const [noderef] <asn:3> *__vpp_verify @@    got const [noderef] <asn:3> *__vpp_verify @@
   net/dsa/slave.c:1106:21: sparse:    expected void const [noderef] <asn:3> *__vpp_verify
   net/dsa/slave.c:1106:21: sparse:    got struct pcpu_sw_netstats *
>> net/dsa/slave.c:1264:6: sparse: sparse: symbol 'dsa_bridge_mtu_normalization' was not declared. Should it be static?
   net/dsa/slave.c:1682:20: sparse: sparse: incorrect type in assignment (different address spaces) @@    expected struct pcpu_sw_netstats *stats64 @@    got struct pcpu_sw_netstruct pcpu_sw_netstats *stats64 @@
   net/dsa/slave.c:1682:20: sparse:    expected struct pcpu_sw_netstats *stats64
   net/dsa/slave.c:1682:20: sparse:    got struct pcpu_sw_netstats [noderef] <asn:3> *pcpu_stats
   net/dsa/slave.c:1726:22: sparse: sparse: incorrect type in argument 1 (different address spaces) @@    expected void [noderef] <asn:3> *__pdata @@    got svoid [noderef] <asn:3> *__pdata @@
   net/dsa/slave.c:1726:22: sparse:    expected void [noderef] <asn:3> *__pdata
   net/dsa/slave.c:1726:22: sparse:    got struct pcpu_sw_netstats *stats64
   net/dsa/slave.c:1745:22: sparse: sparse: incorrect type in argument 1 (different address spaces) @@    expected void [noderef] <asn:3> *__pdata @@    got svoid [noderef] <asn:3> *__pdata @@
   net/dsa/slave.c:1745:22: sparse:    expected void [noderef] <asn:3> *__pdata
   net/dsa/slave.c:1745:22: sparse:    got struct pcpu_sw_netstats *stats64

Please review and possibly fold the followup patch.

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

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: kbuild-all@lists.01.org, andrew@lunn.ch, f.fainelli@gmail.com,
	vivien.didelot@gmail.com, davem@davemloft.net,
	jakub.kicinski@netronome.com, murali.policharla@broadcom.com,
	stephen@networkplumber.org, jiri@resnulli.us, idosch@idosch.org,
	kuba@kernel.org, nikolay@cumulusnetworks.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH v3 net-next 4/8] net: dsa: implement auto-normalization of MTU for bridge hardware datapath
Date: Thu, 2 Apr 2020 09:25:03 +0800	[thread overview]
Message-ID: <20200402012503.GF8179@shao2-debian> (raw)
In-Reply-To: <20200326224040.32014-5-olteanv@gmail.com>

Hi Vladimir,

I love your patch! Perhaps something to improve:

[auto build test WARNING on net-next/master]
[also build test WARNING on linus/master v5.6-rc7 next-20200327]
[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/Vladimir-Oltean/Configure-the-MTU-on-DSA-switches/20200327-094801
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 92b7e62e5630a370955a4760bbeb3967457034ec
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-187-gbff9b106-dirty
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
:::::: branch date: 17 hours ago
:::::: commit date: 17 hours ago

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

   net/dsa/slave.c:506:13: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected void const [noderef] <asn:3> *__vpp_verify @@    got const [noderef] <asn:3> *__vpp_verify @@
   net/dsa/slave.c:506:13: sparse:    expected void const [noderef] <asn:3> *__vpp_verify
   net/dsa/slave.c:506:13: sparse:    got struct pcpu_sw_netstats *
   net/dsa/slave.c:640:21: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected void const [noderef] <asn:3> *__vpp_verify @@    got const [noderef] <asn:3> *__vpp_verify @@
   net/dsa/slave.c:640:21: sparse:    expected void const [noderef] <asn:3> *__vpp_verify
   net/dsa/slave.c:640:21: sparse:    got struct pcpu_sw_netstats *
   net/dsa/slave.c:1106:21: sparse: sparse: incorrect type in initializer (different address spaces) @@    expected void const [noderef] <asn:3> *__vpp_verify @@    got const [noderef] <asn:3> *__vpp_verify @@
   net/dsa/slave.c:1106:21: sparse:    expected void const [noderef] <asn:3> *__vpp_verify
   net/dsa/slave.c:1106:21: sparse:    got struct pcpu_sw_netstats *
>> net/dsa/slave.c:1264:6: sparse: sparse: symbol 'dsa_bridge_mtu_normalization' was not declared. Should it be static?
   net/dsa/slave.c:1682:20: sparse: sparse: incorrect type in assignment (different address spaces) @@    expected struct pcpu_sw_netstats *stats64 @@    got struct pcpu_sw_netstruct pcpu_sw_netstats *stats64 @@
   net/dsa/slave.c:1682:20: sparse:    expected struct pcpu_sw_netstats *stats64
   net/dsa/slave.c:1682:20: sparse:    got struct pcpu_sw_netstats [noderef] <asn:3> *pcpu_stats
   net/dsa/slave.c:1726:22: sparse: sparse: incorrect type in argument 1 (different address spaces) @@    expected void [noderef] <asn:3> *__pdata @@    got svoid [noderef] <asn:3> *__pdata @@
   net/dsa/slave.c:1726:22: sparse:    expected void [noderef] <asn:3> *__pdata
   net/dsa/slave.c:1726:22: sparse:    got struct pcpu_sw_netstats *stats64
   net/dsa/slave.c:1745:22: sparse: sparse: incorrect type in argument 1 (different address spaces) @@    expected void [noderef] <asn:3> *__pdata @@    got svoid [noderef] <asn:3> *__pdata @@
   net/dsa/slave.c:1745:22: sparse:    expected void [noderef] <asn:3> *__pdata
   net/dsa/slave.c:1745:22: sparse:    got struct pcpu_sw_netstats *stats64

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

  reply	other threads:[~2020-04-02  1:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 22:40 [PATCH v3 net-next 0/8] Configure the MTU on DSA switches Vladimir Oltean
2020-03-26 22:40 ` [PATCH v3 net-next 1/8] net: phy: bcm7xx: add jumbo frame configuration to PHY Vladimir Oltean
2020-03-26 23:17   ` Florian Fainelli
2020-03-26 22:40 ` [PATCH v3 net-next 2/8] bgmac: configure MTU and add support for frames beyond 8192 byte size Vladimir Oltean
2020-03-26 22:40 ` [PATCH v3 net-next 3/8] net: dsa: configure the MTU for switch ports Vladimir Oltean
2020-03-27  0:06   ` Andrew Lunn
2020-03-27 10:00     ` Vladimir Oltean
2020-03-26 22:40 ` [PATCH v3 net-next 4/8] net: dsa: implement auto-normalization of MTU for bridge hardware datapath Vladimir Oltean
2020-04-02  1:25   ` kbuild test robot [this message]
2020-04-02  1:25     ` kbuild test robot
2020-03-26 22:40 ` [PATCH v3 net-next 5/8] net: dsa: b53: add MTU configuration support Vladimir Oltean
2020-03-26 23:16   ` Florian Fainelli
2020-03-27 13:01     ` Vladimir Oltean
2020-03-26 22:40 ` [PATCH v3 net-next 6/8] net: dsa: sja1105: implement the port MTU callbacks Vladimir Oltean
2020-03-26 22:40 ` [PATCH v3 net-next 7/8] net: dsa: vsc73xx: make the MTU configurable Vladimir Oltean
2020-03-26 22:40 ` [PATCH v3 net-next 8/8] net: dsa: felix: support changing the MTU Vladimir Oltean

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=20200402012503.GF8179@shao2-debian \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.