[mkl-can-next:testing 42/51] drivers/net/can/dev/bittiming.c:79:24: error: too many arguments to function 'can_calc_bittiming'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git testing
head:   3dafbe5cc1409dd2e3fc2955b0026c1ba7dfa323
commit: 286c0e09e8e07de0f116a01aa234b05d9956dcf5 [42/51] can: bittiming: can_changelink() pass extack down callstack
config: parisc-randconfig-r026-20230205 (https://download.01.org/0day-ci/archive/20230208/202302080358.PGPjdXwE-lkp@xxxxxxxxx/config)
compiler: hppa-linux-gcc (GCC) 12.1.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://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git/commit/?id=286c0e09e8e07de0f116a01aa234b05d9956dcf5
        git remote add mkl-can-next https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git
        git fetch --no-tags mkl-can-next testing
        git checkout 286c0e09e8e07de0f116a01aa234b05d9956dcf5
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash drivers/net/can/dev/

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@xxxxxxxxx>

All errors (new ones prefixed by >>):

   drivers/net/can/dev/bittiming.c: In function 'can_get_bittiming':
>> drivers/net/can/dev/bittiming.c:79:24: error: too many arguments to function 'can_calc_bittiming'
      79 |                 return can_calc_bittiming(dev, bt, btc, extack);
         |                        ^~~~~~~~~~~~~~~~~~
   In file included from include/linux/can/dev.h:18,
                    from drivers/net/can/dev/bittiming.c:7:
   include/linux/can/bittiming.h:126:1: note: declared here
     126 | can_calc_bittiming(const struct net_device *dev, struct can_bittiming *bt,
         | ^~~~~~~~~~~~~~~~~~


vim +/can_calc_bittiming +79 drivers/net/can/dev/bittiming.c

    66	
    67	int can_get_bittiming(const struct net_device *dev, struct can_bittiming *bt,
    68			      const struct can_bittiming_const *btc,
    69			      const u32 *bitrate_const,
    70			      const unsigned int bitrate_const_cnt,
    71			      struct netlink_ext_ack *extack)
    72	{
    73		/* Depending on the given can_bittiming parameter structure the CAN
    74		 * timing parameters are calculated based on the provided bitrate OR
    75		 * alternatively the CAN timing parameters (tq, prop_seg, etc.) are
    76		 * provided directly which are then checked and fixed up.
    77		 */
    78		if (!bt->tq && bt->bitrate && btc)
  > 79			return can_calc_bittiming(dev, bt, btc, extack);

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests



[Index of Archives]     [Automotive Discussions]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [CAN Bus]

  Powered by Linux