netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Aleksander Jan Bajkowski <olek2@wp.pl>,
	hauke@hauke-m.de, andrew@lunn.ch, vivien.didelot@gmail.com,
	f.fainelli@gmail.com, olteanv@gmail.com, davem@davemloft.net,
	kuba@kernel.org, robh+dt@kernel.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 1/2] net: dsa: lantiq: allow to use all GPHYs on xRX300 and xRX330
Date: Thu, 10 Dec 2020 16:20:18 +0800	[thread overview]
Message-ID: <202012101615.iwDJYpoV-lkp@intel.com> (raw)
In-Reply-To: <20201206132713.13452-2-olek2@wp.pl>

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

Hi Aleksander,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on robh/for-next]
[also build test WARNING on net-next/master net/master linus/master sparc-next/master v5.10-rc7 next-20201209]
[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/Aleksander-Jan-Bajkowski/net-dsa-lantiq-add-support-for-xRX300-and-xRX330/20201206-213318
base:   https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: parisc-randconfig-r033-20201209 (attached as .config)
compiler: hppa-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/3a3400f9d3cd41f2b72cd741f208a70fca7fe93f
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Aleksander-Jan-Bajkowski/net-dsa-lantiq-add-support-for-xRX300-and-xRX330/20201206-213318
        git checkout 3a3400f9d3cd41f2b72cd741f208a70fca7fe93f
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc 

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

All warnings (new ones prefixed by >>):

   In file included from include/linux/kasan-checks.h:5,
                    from include/asm-generic/rwonce.h:26,
                    from ./arch/parisc/include/generated/asm/rwonce.h:1,
                    from include/linux/compiler.h:232,
                    from include/linux/err.h:5,
                    from include/linux/clk.h:12,
                    from drivers/net/dsa/lantiq_gswip.c:28:
   drivers/net/dsa/lantiq_gswip.c: In function 'gswip_xrx300_phylink_validate':
   drivers/net/dsa/lantiq_gswip.c:1495:35: warning: unused variable 'mask' [-Wunused-variable]
    1495 |  __ETHTOOL_DECLARE_LINK_MODE_MASK(mask) = { 0, };
         |                                   ^~~~
   include/linux/types.h:11:16: note: in definition of macro 'DECLARE_BITMAP'
      11 |  unsigned long name[BITS_TO_LONGS(bits)]
         |                ^~~~
   drivers/net/dsa/lantiq_gswip.c:1495:2: note: in expansion of macro '__ETHTOOL_DECLARE_LINK_MODE_MASK'
    1495 |  __ETHTOOL_DECLARE_LINK_MODE_MASK(mask) = { 0, };
         |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   drivers/net/dsa/lantiq_gswip.c: At top level:
>> drivers/net/dsa/lantiq_gswip.c:2068:9: warning: initialization discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
    2068 |  .ops = &gswip_xrx200_switch_ops,
         |         ^
   drivers/net/dsa/lantiq_gswip.c:2074:9: warning: initialization discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
    2074 |  .ops = &gswip_xrx300_switch_ops,
         |         ^
   drivers/net/dsa/lantiq_gswip.c:1741:34: warning: 'xway_gphy_match' defined but not used [-Wunused-const-variable=]
    1741 | static const struct of_device_id xway_gphy_match[] = {
         |                                  ^~~~~~~~~~~~~~~

vim +/const +2068 drivers/net/dsa/lantiq_gswip.c

  2064	
  2065	static const struct gswip_hw_info gswip_xrx200 = {
  2066		.max_ports = 7,
  2067		.cpu_port = 6,
> 2068		.ops = &gswip_xrx200_switch_ops,
  2069	};
  2070	

---
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: 28862 bytes --]

  parent reply	other threads:[~2020-12-10  8:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 13:27 [PATCH v2 0/2] net: dsa: lantiq: add support for xRX300 and xRX330 Aleksander Jan Bajkowski
2020-12-06 13:27 ` [PATCH v2 1/2] net: dsa: lantiq: allow to use all GPHYs on " Aleksander Jan Bajkowski
2020-12-06 18:54   ` Vladimir Oltean
2020-12-07 21:43   ` Jakub Kicinski
2020-12-09 14:46   ` kernel test robot
2020-12-10  8:20   ` kernel test robot [this message]
2020-12-06 13:27 ` [PATCH v2 2/2] dt-bindings: net: dsa: lantiq, lantiq-gswip: add example for xRX330 Aleksander Jan Bajkowski
2020-12-10  3:40   ` Rob Herring

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=202012101615.iwDJYpoV-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=kbuild-all@lists.01.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olek2@wp.pl \
    --cc=olteanv@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=vivien.didelot@gmail.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).