public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org
Subject: [rmk-arm:zii 35/107] drivers/net/phy/phylink.c:1328: warning: expecting prototype for phylink_set_fixe_linkd(). Prototype was for phylink_set_fixed_link() instead
Date: Wed, 22 Jun 2022 13:04:36 +0800	[thread overview]
Message-ID: <202206221232.Go3hwcU6-lkp@intel.com> (raw)

tree:   git://git.armlinux.org.uk/~rmk/linux-arm zii
head:   aedc75cf78fca1c8b7052c5d59981354f47e2e48
commit: 5c17680ea9fcb1a7cf664279fe1bcf51934dcdaa [35/107] net: phylink: add phylink_set_fixed_link()
config: x86_64-randconfig-a016 (https://download.01.org/0day-ci/archive/20220622/202206221232.Go3hwcU6-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 8b8d126598ce7bd5243da7f94f69fa1104288bee)
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
        git remote add rmk-arm git://git.armlinux.org.uk/~rmk/linux-arm
        git fetch --no-tags rmk-arm zii
        git checkout 5c17680ea9fcb1a7cf664279fe1bcf51934dcdaa
        # 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=x86_64 SHELL=/bin/bash drivers/net/phy/

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

All warnings (new ones prefixed by >>):

>> drivers/net/phy/phylink.c:1328: warning: expecting prototype for phylink_set_fixe_linkd(). Prototype was for phylink_set_fixed_link() instead


vim +1328 drivers/net/phy/phylink.c

  1317	
  1318	/**
  1319	 * phylink_set_fixe_linkd() - set a fixed link configuration for phylink
  1320	 * @pl: a pointer to a &struct phylink returned from phylink_create()
  1321	 * @speed: a SPEED_xx constant
  1322	 * @duplex: DUPLEX_FULL or DUPLEX_HALF
  1323	 *
  1324	 * Set a fixed-link configuration for the phylink instance immediately
  1325	 * after creation. Must not be used at any other time.
  1326	 */
  1327	int phylink_set_fixed_link(struct phylink *pl, int speed, int duplex)
> 1328	{
  1329		if (pl->cfg_link_an_mode != MLO_AN_PHY || pl->phydev || pl->sfp_bus)
  1330			return -EINVAL;
  1331	
  1332		pl->link_config.speed = speed;
  1333		pl->link_config.duplex = duplex;
  1334		pl->link_config.link = 1;
  1335		pl->cfg_link_an_mode = MLO_AN_FIXED;
  1336		pl->cur_link_an_mode = MLO_AN_FIXED;
  1337	
  1338		return 0;
  1339	}
  1340	EXPORT_SYMBOL_GPL(phylink_set_fixed_link);
  1341	

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

             reply	other threads:[~2022-06-22  5:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  5:04 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-22  0:29 [rmk-arm:zii 35/107] drivers/net/phy/phylink.c:1328: warning: expecting prototype for phylink_set_fixe_linkd(). Prototype was for phylink_set_fixed_link() instead kernel test robot

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=202206221232.Go3hwcU6-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=rmk+kernel@armlinux.org.uk \
    /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