devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: eajames <eajames@linux.vnet.ibm.com>
To: "Edward A. James" <eajames@us.ibm.com>
Cc: linux@roeck-us.net, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
	linux-doc@vger.kernel.org, jdelvare@suse.com, corbet@lwn.net,
	mark.rutland@arm.com, robh+dt@kernel.org, wsa@the-dreams.de,
	andrew@aj.id.au, joel@jms.id.au, benh@kernel.crashing.org
Subject: Re: [PATCH linux v6 1/6] hwmon: Add core On-Chip Controller support for POWER CPUs
Date: Tue, 07 Feb 2017 17:11:25 -0600	[thread overview]
Message-ID: <20a5cf57f31190f76db1dbdf018c86ed@linux.vnet.ibm.com> (raw)
In-Reply-To: <201702070705.HAlnLg64%fengguang.wu@intel.com>

Pushing up v7 to fix this compile warning. No other changes.

On 2017-02-06 17:21, kbuild test robot wrote:
> Hi Edward,
> 
> [auto build test WARNING on hwmon/hwmon-next]
> [also build test WARNING on v4.10-rc7 next-20170206]
> [cannot apply to linux/master]
> [if your patch is applied to the wrong git tree, please drop us a note
> to help improve the system]
> 
> url:
> https://github.com/0day-ci/linux/commits/eajames-linux-vnet-ibm-com/drivers-hwmon-Add-On-Chip-Controller-driver/20170207-043353
> base:
> https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
> hwmon-next
> config: openrisc-allyesconfig (attached as .config)
> compiler: or32-linux-gcc (GCC) 4.5.1-or32-1.0rc1
> reproduce:
>         wget
> https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
> -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # save the attached .config to linux build tree
>         make.cross ARCH=openrisc
> 
> All warnings (new ones prefixed by >>):
> 
>    drivers/hwmon/occ/occ.c: In function 'parse_occ_response':
>>> drivers/hwmon/occ/occ.c:127:6: warning: unused variable 'rc'
> 
> vim +/rc +127 drivers/hwmon/occ/occ.c
> 
>    111		struct device *dev;
>    112		void *bus;
>    113		struct occ_bus_ops bus_ops;
>    114		struct occ_ops ops;
>    115		struct occ_config config;
>    116		unsigned long last_updated;
>    117		struct mutex update_lock;
>    118		struct occ_response response;
>    119		bool valid;
>    120		u8 *raw_data;
>    121	};
>    122
>    123	static int parse_occ_response(struct occ *driver, u16 num_bytes)
>    124	{
>    125		int b;
>    126		int s;
>  > 127		int rc;
>    128		unsigned int offset = SENSOR_BLOCK_OFFSET;
>    129		int sensor_type;
>    130		u8 num_sensor_blocks;
>    131		struct sensor_data_block_header *block;
>    132		void *sensors;
>    133		struct device *dev = driver->dev;
>    134		u8 *data = driver->raw_data;
>    135		struct occ_response *resp = &driver->response;
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology 
> Center
> https://lists.01.org/pipermail/kbuild-all                   Intel 
> Corporation


  reply	other threads:[~2017-02-07 23:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 20:27 [PATCH linux v6 0/6] drivers: hwmon: Add On-Chip Controller driver eajames-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8
2017-02-06 20:27 ` [PATCH linux v6 1/6] hwmon: Add core On-Chip Controller support for POWER CPUs eajames
2017-02-06 23:21   ` kbuild test robot
2017-02-07 23:11     ` eajames [this message]
2017-02-06 20:27 ` [PATCH linux v6 2/6] hwmon: occ: Add sysfs interface eajames
2017-02-06 20:27 ` [PATCH linux v6 3/6] hwmon: occ: Add I2C transport implementation for SCOM operations eajames
2017-02-06 20:27 ` [PATCH linux v6 4/6] hwmon: occ: Add callbacks for parsing P8 OCC datastructures eajames
2017-02-06 20:27 ` [PATCH linux v6 5/6] hwmon: occ: Add hwmon implementation for the P8 OCC eajames
     [not found] ` <1486412832-21854-1-git-send-email-eajames-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-02-06 20:27   ` [PATCH linux v6 6/6] hwmon: occ: Add callbacks for parsing P9 OCC datastructures eajames-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8

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=20a5cf57f31190f76db1dbdf018c86ed@linux.vnet.ibm.com \
    --to=eajames@linux.vnet.ibm.com \
    --cc=andrew@aj.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=eajames@us.ibm.com \
    --cc=jdelvare@suse.com \
    --cc=joel@jms.id.au \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=wsa@the-dreams.de \
    /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).