All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: sunil.kovvuri@gmail.com
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org,
	davem@davemloft.net, Sunil Goutham <sgoutham@marvell.com>
Subject: Re: [PATCH 01/17] octeontx2-pf: Add Marvell OcteonTX2 NIC driver
Date: Sun, 12 Jan 2020 18:01:07 +0800	[thread overview]
Message-ID: <202001121724.dYvIz3uX%lkp@intel.com> (raw)
In-Reply-To: <1578656521-14189-2-git-send-email-sunil.kovvuri@gmail.com>

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

Hi,

I love your patch! Yet something to improve:

[auto build test ERROR on net/master]
[also build test ERROR on net-next/master linus/master v5.5-rc5 next-20200110]
[cannot apply to ipvs/master sparc-next/master]
[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/sunil-kovvuri-gmail-com/octeontx2-pf-Add-network-driver-for-physical-function/20200111-050500
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git e267371dd376d1b3ebc9f01229845a9656734d97
config: mips-allmodconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 7.5.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.5.0 make.cross ARCH=mips 

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

All errors (new ones prefixed by >>):

   drivers/net/ethernet/marvell/octeontx2/af/mbox.c: In function 'otx2_mbox_msg_send':
>> drivers/net/ethernet/marvell/octeontx2/af/mbox.c:207:2: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
     writeq(1, (void __iomem *)mbox->reg_base +
     ^~~~~~
     writel
   cc1: some warnings being treated as errors
--
   In file included from drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c:20:0:
   drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h: In function 'otx2_write64':
>> drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h:67:2: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
     writeq(val, addr);
     ^~~~~~
     writel
   drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h: In function 'otx2_read64':
>> drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h:74:9: error: implicit declaration of function 'readq'; did you mean 'readl'? [-Werror=implicit-function-declaration]
     return readq(addr);
            ^~~~~
            readl
   cc1: some warnings being treated as errors

vim +67 drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h

    62	
    63	static inline void otx2_write64(struct otx2_nic *nic, u64 offset, u64 val)
    64	{
    65		void __iomem *addr = otx2_get_regaddr(nic, offset);
    66	
  > 67		writeq(val, addr);
    68	}
    69	
    70	static inline u64 otx2_read64(struct otx2_nic *nic, u64 offset)
    71	{
    72		void __iomem *addr = otx2_get_regaddr(nic, offset);
    73	
  > 74		return readq(addr);
    75	}
    76	

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation

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

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 01/17] octeontx2-pf: Add Marvell OcteonTX2 NIC driver
Date: Sun, 12 Jan 2020 18:01:07 +0800	[thread overview]
Message-ID: <202001121724.dYvIz3uX%lkp@intel.com> (raw)
In-Reply-To: <1578656521-14189-2-git-send-email-sunil.kovvuri@gmail.com>

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

Hi,

I love your patch! Yet something to improve:

[auto build test ERROR on net/master]
[also build test ERROR on net-next/master linus/master v5.5-rc5 next-20200110]
[cannot apply to ipvs/master sparc-next/master]
[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/sunil-kovvuri-gmail-com/octeontx2-pf-Add-network-driver-for-physical-function/20200111-050500
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git e267371dd376d1b3ebc9f01229845a9656734d97
config: mips-allmodconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 7.5.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.5.0 make.cross ARCH=mips 

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

All errors (new ones prefixed by >>):

   drivers/net/ethernet/marvell/octeontx2/af/mbox.c: In function 'otx2_mbox_msg_send':
>> drivers/net/ethernet/marvell/octeontx2/af/mbox.c:207:2: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
     writeq(1, (void __iomem *)mbox->reg_base +
     ^~~~~~
     writel
   cc1: some warnings being treated as errors
--
   In file included from drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c:20:0:
   drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h: In function 'otx2_write64':
>> drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h:67:2: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
     writeq(val, addr);
     ^~~~~~
     writel
   drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h: In function 'otx2_read64':
>> drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h:74:9: error: implicit declaration of function 'readq'; did you mean 'readl'? [-Werror=implicit-function-declaration]
     return readq(addr);
            ^~~~~
            readl
   cc1: some warnings being treated as errors

vim +67 drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h

    62	
    63	static inline void otx2_write64(struct otx2_nic *nic, u64 offset, u64 val)
    64	{
    65		void __iomem *addr = otx2_get_regaddr(nic, offset);
    66	
  > 67		writeq(val, addr);
    68	}
    69	
    70	static inline u64 otx2_read64(struct otx2_nic *nic, u64 offset)
    71	{
    72		void __iomem *addr = otx2_get_regaddr(nic, offset);
    73	
  > 74		return readq(addr);
    75	}
    76	

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation

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

  reply	other threads:[~2020-01-12 10:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 11:41 [PATCH 00/17] octeontx2-pf: Add network driver for physical function sunil.kovvuri
2020-01-10 11:41 ` [PATCH 01/17] octeontx2-pf: Add Marvell OcteonTX2 NIC driver sunil.kovvuri
2020-01-12 10:01   ` kbuild test robot [this message]
2020-01-12 10:01     ` kbuild test robot
2020-01-12 18:52   ` kbuild test robot
2020-01-12 18:52     ` kbuild test robot
2020-01-10 11:41 ` [PATCH 02/17] octeontx2-pf: Mailbox communication with AF sunil.kovvuri
2020-01-10 11:41 ` [PATCH 03/17] octeontx2-pf: Attach NIX and NPA block LFs sunil.kovvuri
2020-01-10 11:41 ` [PATCH 04/17] octeontx2-pf: Initialize and config queues sunil.kovvuri
2020-01-12 17:01   ` kbuild test robot
2020-01-12 17:01     ` kbuild test robot
2020-01-10 11:41 ` [PATCH 05/17] octeontx2-pf: Setup interrupts and NAPI handler sunil.kovvuri
2020-01-10 11:41 ` [PATCH 06/17] octeontx2-pf: Receive packet handling support sunil.kovvuri
2020-01-10 11:41 ` [PATCH 07/17] octeontx2-pf: Add packet transmission support sunil.kovvuri
2020-01-13  2:04   ` kbuild test robot
2020-01-13  2:04     ` kbuild test robot
2020-01-10 11:41 ` [PATCH 08/17] octeontx2-pf: Register and handle link notifications sunil.kovvuri
2020-01-10 11:41 ` [PATCH 09/17] octeontx2-pf: MTU, MAC and RX mode config support sunil.kovvuri
2020-01-10 11:41 ` [PATCH 10/17] octeontx2-pf: Error handling support sunil.kovvuri
2020-01-10 11:41 ` [PATCH 11/17] octeontx2-pf: Receive side scaling support sunil.kovvuri
2020-01-10 11:41 ` [PATCH 12/17] octeontx2-pf: TCP segmentation offload support sunil.kovvuri
2020-01-10 11:41 ` [PATCH 13/17] octeontx2-pf: Add ndo_get_stats64 sunil.kovvuri
2020-01-10 11:41 ` [PATCH 14/17] octeontx2-pf: Add basic ethtool support sunil.kovvuri
2020-01-10 19:28   ` Jakub Kicinski
2020-01-11  8:47     ` Sunil Kovvuri
2020-01-11 13:27       ` Jakub Kicinski
2020-01-13 11:27         ` Sunil Kovvuri
2020-01-10 11:41 ` [PATCH 15/17] octeontx2-pf: ethtool RSS config support sunil.kovvuri
2020-01-10 11:42 ` [PATCH 16/17] Documentation: net: octeontx2: Add RVU HW and drivers overview sunil.kovvuri
2020-01-10 11:42 ` [PATCH 17/17] MAINTAINERS: Add entry for Marvell OcteonTX2 Physical Function driver sunil.kovvuri

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=202001121724.dYvIz3uX%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=kbuild-all@lists.01.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgoutham@marvell.com \
    --cc=sunil.kovvuri@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 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.