LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Tony Lindgren <tony@atomide.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Rob Herring <robh@kernel.org>
Subject: drivers/phy/motorola/phy-mapphone-mdm6600.c:188:16: warning:  is used uninitialized in this function
Date: Thu, 31 May 2018 20:23:44 +0800	[thread overview]
Message-ID: <201805312039.Rlh8ef3G%fengguang.wu@intel.com> (raw)

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

Hi Tony,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   88a867653065dc14b0fdeeb626efb8d7ebe39be5
commit: 5d1ebbda0318b1ba55eaa1fae3fd867af17b0774 phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4
date:   3 months ago
config: x86_64-randconfig-s5-05311957 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
        git checkout 5d1ebbda0318b1ba55eaa1fae3fd867af17b0774
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

   #'target_mem_ref' not supported by expression#'drivers/phy/motorola/phy-mapphone-mdm6600.c: In function 'phy_mdm6600_status':
>> drivers/phy/motorola/phy-mapphone-mdm6600.c:188:16: warning:  is used uninitialized in this function [-Wuninitialized]
      val |= values[i] << i;
             ~~~~~~^~~

vim +188 drivers/phy/motorola/phy-mapphone-mdm6600.c

   166	
   167	/**
   168	 * phy_mdm6600_status() - read mdm6600 status lines
   169	 * @ddata: device driver data
   170	 */
   171	static void phy_mdm6600_status(struct work_struct *work)
   172	{
   173		struct phy_mdm6600 *ddata;
   174		struct device *dev;
   175		int values[PHY_MDM6600_NR_STATUS_LINES];
   176		int error, i, val = 0;
   177	
   178		ddata = container_of(work, struct phy_mdm6600, status_work.work);
   179		dev = ddata->dev;
   180	
   181		error = gpiod_get_array_value_cansleep(PHY_MDM6600_NR_CMD_LINES,
   182						       ddata->status_gpios->desc,
   183						       values);
   184		if (error)
   185			return;
   186	
   187		for (i = 0; i < PHY_MDM6600_NR_CMD_LINES; i++) {
 > 188			val |= values[i] << i;
   189			dev_dbg(ddata->dev, "XXX %s: i: %i values[i]: %i val: %i\n",
   190				__func__, i, values[i], val);
   191		}
   192		ddata->status = val;
   193	
   194		dev_info(dev, "modem status: %i %s\n",
   195			 ddata->status,
   196			 phy_mdm6600_status_name[ddata->status & 7]);
   197		complete(&ddata->ack);
   198	}
   199	

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

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

             reply	other threads:[~2018-05-31 12:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 12:23 kbuild test robot [this message]
2018-05-31 17:08 ` Tony Lindgren
  -- strict thread matches above, loose matches on Subject: below --
2018-04-18 17:46 kbuild test robot
2018-04-27 16:05 ` Tony Lindgren

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=201805312039.Rlh8ef3G%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tony@atomide.com \
    --subject='Re: drivers/phy/motorola/phy-mapphone-mdm6600.c:188:16: warning:  is used uninitialized in this function' \
    /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

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).