public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Gerhard Engleder <gerhard@engleder-embedded.com>,
	linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	arnd@arndb.de, gregkh@linuxfoundation.org,
	Gerhard Engleder <gerhard@engleder-embedded.com>
Subject: Re: [PATCH 2/6] misc: keba: Add LAN9252 driver
Date: Fri, 11 Oct 2024 16:28:07 +0800	[thread overview]
Message-ID: <202410111611.EMSfFrYK-lkp@intel.com> (raw)
In-Reply-To: <20241009202949.20164-3-gerhard@engleder-embedded.com>

Hi Gerhard,

kernel test robot noticed the following build warnings:

[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on char-misc/char-misc-next char-misc/char-misc-linus linus/master v6.12-rc2 next-20241010]
[cannot apply to soc/for-next]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Gerhard-Engleder/misc-keba-Add-SPI-controller-device/20241010-051016
base:   char-misc/char-misc-testing
patch link:    https://lore.kernel.org/r/20241009202949.20164-3-gerhard%40engleder-embedded.com
patch subject: [PATCH 2/6] misc: keba: Add LAN9252 driver
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20241011/202410111611.EMSfFrYK-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241011/202410111611.EMSfFrYK-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202410111611.EMSfFrYK-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/misc/keba/lan9252.c:299:10: warning: variable 'ret' is uninitialized when used here [-Wuninitialized]
     299 |                 return ret;
         |                        ^~~
   drivers/misc/keba/lan9252.c:291:9: note: initialize the variable 'ret' to silence this warning
     291 |         int ret;
         |                ^
         |                 = 0
   1 warning generated.


vim +/ret +299 drivers/misc/keba/lan9252.c

   286	
   287	static int lan9252_probe(struct spi_device *spi)
   288	{
   289		u32 data;
   290		int retry = SPI_RETRY_COUNT;
   291		int ret;
   292	
   293		/* execute specified initialization sequence */
   294		while (retry && !lan9252_init(spi))
   295			retry--;
   296		if (retry == 0) {
   297			dev_err(&spi->dev,
   298				"Can't initialize LAN9252 SPI communication!");
 > 299			return ret;
   300		}
   301	
   302		/* enable access to MII management for PDI */
   303		ret = lan9252_access_mii(spi, true);
   304		if (ret) {
   305			dev_err(&spi->dev, "Can't enable access to MII management!");
   306			return ret;
   307		}
   308	
   309		/*
   310		 * check PHY configuration and configure if necessary
   311		 *	- full duplex
   312		 *	- auto negotiation disabled
   313		 *	- 100 Mbps
   314		 */
   315		ret = lan9252_mii_read(spi, PHY_ADDRESS, MII_BMCR, &data);
   316		if (ret) {
   317			dev_err(&spi->dev, "Can't read LAN9252 configuration!");
   318			goto out;
   319		}
   320		if (!(data & BMCR_FULLDPLX) || (data & BMCR_ANENABLE) ||
   321		    !(data & BMCR_SPEED100)) {
   322			/*
   323			 */
   324			data &= ~(BMCR_ANENABLE);
   325			data |= (BMCR_FULLDPLX | BMCR_SPEED100);
   326			ret = lan9252_mii_write(spi, PHY_ADDRESS, MII_BMCR, data);
   327			if (ret)
   328				dev_err(&spi->dev,
   329					"Can't write LAN9252 configuration!");
   330		}
   331	
   332		dev_info(&spi->dev, "LAN9252 PHY configuration");
   333	
   334	out:
   335		/* disable access to MII management for PDI */
   336		lan9252_access_mii(spi, false);
   337	
   338		return ret;
   339	}
   340	

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

  reply	other threads:[~2024-10-11  8:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 20:29 [PATCH 0/6] misc: keba: Add support for additional devices Gerhard Engleder
2024-10-09 20:29 ` [PATCH 1/6] misc: keba: Add SPI controller device Gerhard Engleder
2024-10-10  7:12   ` Greg KH
2024-10-10 19:53     ` Gerhard Engleder
2024-10-13  1:03   ` kernel test robot
2024-10-09 20:29 ` [PATCH 2/6] misc: keba: Add LAN9252 driver Gerhard Engleder
2024-10-11  8:28   ` kernel test robot [this message]
2024-10-09 20:29 ` [PATCH 3/6] misc: keba: Support EEPROM sections as separate devices Gerhard Engleder
2024-10-13  8:52   ` kernel test robot
2024-10-09 20:29 ` [PATCH 4/6] misc: keba: Add fan device Gerhard Engleder
2024-10-09 20:29 ` [PATCH 5/6] misc: keba: Add battery device Gerhard Engleder
2024-10-09 20:29 ` [PATCH 6/6] misc: keba: Add UART devices Gerhard Engleder

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=202410111611.EMSfFrYK-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=arnd@arndb.de \
    --cc=gerhard@engleder-embedded.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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