netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>,
	netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	outreachy@lists.linux.dev, roopa@nvidia.com, jdenham@redhat.com,
	sbrivio@redhat.com, jesse.brandeburg@intel.com,
	anthony.l.nguyen@intel.com, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, vladimir.oltean@nxp.com,
	claudiu.manoil@nxp.com, alexandre.belloni@bootlin.com,
	shshaikh@marvell.com, manishc@marvell.com, razor@blackwall.org,
	intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org,
	UNGLinuxDriver@microchip.com, GR-Linux-NIC-Dev@marvell.com,
	bridge@lists.linux-foundation.org,
	eng.alaamohamedsoliman.am@gmail.com
Subject: Re: [PATCH net-next v4 1/2] rtnetlink: add extack support in fdb del handlers
Date: Tue, 26 Apr 2022 18:23:14 +0800	[thread overview]
Message-ID: <202204261831.S6mBmtgP-lkp@intel.com> (raw)
In-Reply-To: <8847c5d670c7ee11890d75f58a4922c5cb542f20.1650896000.git.eng.alaamohamedsoliman.am@gmail.com>

Hi Alaa,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on horms-ipvs/master]
[also build test ERROR on net/master linus/master v5.18-rc4]
[cannot apply to net-next/master next-20220422]
[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/intel-lab-lkp/linux/commits/Alaa-Mohamed/propagate-extack-to-vxlan_fdb_delete/20220425-222644
base:   https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs.git master
config: riscv-randconfig-r002-20220425 (https://download.01.org/0day-ci/archive/20220426/202204261831.S6mBmtgP-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 1cddcfdc3c683b393df1a5c9063252eb60e52818)
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
        # install riscv cross compiling tool for clang build
        # apt-get install binutils-riscv64-linux-gnu
        # https://github.com/intel-lab-lkp/linux/commit/5e9c3e146040a4e37b45ca18c3b42c3dfd6d0a0e
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Alaa-Mohamed/propagate-extack-to-vxlan_fdb_delete/20220425-222644
        git checkout 5e9c3e146040a4e37b45ca18c3b42c3dfd6d0a0e
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash drivers/net/ethernet/mscc/

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

All errors (new ones prefixed by >>):

>> drivers/net/ethernet/mscc/ocelot_net.c:784:70: error: too many arguments to function call, expected 5, have 6
           return ocelot_fdb_del(ocelot, port, addr, vid, ocelot_port->bridge, extack);
                  ~~~~~~~~~~~~~~                                               ^~~~~~
   include/soc/mscc/ocelot.h:893:5: note: 'ocelot_fdb_del' declared here
   int ocelot_fdb_del(struct ocelot *ocelot, int port, const unsigned char *addr,
       ^
   1 error generated.


vim +784 drivers/net/ethernet/mscc/ocelot_net.c

   774	
   775	static int ocelot_port_fdb_del(struct ndmsg *ndm, struct nlattr *tb[],
   776				       struct net_device *dev,
   777				       const unsigned char *addr, u16 vid, struct netlink_ext_ack *extack)
   778	{
   779		struct ocelot_port_private *priv = netdev_priv(dev);
   780		struct ocelot_port *ocelot_port = &priv->port;
   781		struct ocelot *ocelot = ocelot_port->ocelot;
   782		int port = priv->chip_port;
   783	
 > 784		return ocelot_fdb_del(ocelot, port, addr, vid, ocelot_port->bridge, extack);
   785	}
   786	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

  reply	other threads:[~2022-04-26 10:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 14:25 [PATCH net-next v4 0/2] propagate extack to vxlan_fdb_delete Alaa Mohamed
2022-04-25 14:25 ` [PATCH net-next v4 1/2] rtnetlink: add extack support in fdb del handlers Alaa Mohamed
2022-04-26 10:23   ` kernel test robot [this message]
2022-04-25 14:25 ` [PATCH net-next v4 2/2] net: vxlan: vxlan_core.c: Add extack support to vxlan_fdb_delete Alaa Mohamed
2022-04-25 15:48 ` [PATCH net-next v4 0/2] propagate extack " Jakub Kicinski

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=202204261831.S6mBmtgP-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=GR-Linux-NIC-Dev@marvell.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=eng.alaamohamedsoliman.am@gmail.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jdenham@redhat.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=manishc@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=outreachy@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.com \
    --cc=sbrivio@redhat.com \
    --cc=shshaikh@marvell.com \
    --cc=vladimir.oltean@nxp.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).