linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Luca Ceresoli <luca@lucaceresoli.net>
Cc: kbuild-all@01.org, linux-media@vger.kernel.org,
	Luca Ceresoli <luca@lucaceresoli.net>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Leon Luo <leonl@leopardimaging.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] media: imx274: use regmap_bulk_write to write multybyte registers
Date: Sat, 14 Jul 2018 02:46:22 +0800	[thread overview]
Message-ID: <201807140225.cKmtgIPL%fengguang.wu@intel.com> (raw)
In-Reply-To: <1530801489-29953-2-git-send-email-luca@lucaceresoli.net>

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

Hi Luca,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on next-20180713]
[cannot apply to v4.18-rc4]
[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/Luca-Ceresoli/media-imx274-cleanups-improvements-and-SELECTION-API-support/20180706-032128
base:   git://linuxtv.org/media_tree.git master
config: i386-randconfig-sb0-07140141 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   drivers/media/i2c/imx274.c: In function 'imx274_write_mbreg':
>> drivers/media/i2c/imx274.c:714:4: warning: format '%ld' expects argument of type 'long int', but argument 6 has type 'size_t' [-Wformat=]
       __func__, addr, val, nbytes);
       ^
   drivers/media/i2c/imx274.c:716:3: warning: format '%ld' expects argument of type 'long int', but argument 7 has type 'size_t' [-Wformat=]
      dev_dbg(&priv->client->dev,
      ^

vim +714 drivers/media/i2c/imx274.c

   692	
   693	/**
   694	 * Write a multibyte register.
   695	 *
   696	 * Uses a bulk write where possible.
   697	 *
   698	 * @priv: Pointer to device structure
   699	 * @addr: Address of the LSB register.  Other registers must be
   700	 *        consecutive, least-to-most significant.
   701	 * @val: Value to be written to the register (cpu endianness)
   702	 * @nbytes: Number of bits to write (range: [1..3])
   703	 */
   704	static int imx274_write_mbreg(struct stimx274 *priv, u16 addr, u32 val,
   705				      size_t nbytes)
   706	{
   707		__le32 val_le = cpu_to_le32(val);
   708		int err;
   709	
   710		err = regmap_bulk_write(priv->regmap, addr, &val_le, nbytes);
   711		if (err)
   712			dev_err(&priv->client->dev,
   713				"%s : i2c bulk write failed, %x = %x (%ld bytes)\n",
 > 714				__func__, addr, val, nbytes);
   715		else
   716			dev_dbg(&priv->client->dev,
   717				"%s : addr 0x%x, val=0x%x (%ld bytes)\n",
   718				__func__, addr, val, nbytes);
   719		return err;
   720	}
   721	

---
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: 30625 bytes --]

  reply	other threads:[~2018-07-13 18:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05 14:38 [PATCH v5 0/2] media: imx274: cleanups, improvements and SELECTION API support Luca Ceresoli
2018-07-05 14:38 ` [PATCH v5 1/2] media: imx274: use regmap_bulk_write to write multybyte registers Luca Ceresoli
2018-07-13 18:46   ` kbuild test robot [this message]
2018-07-05 14:38 ` [PATCH v5 2/2] media: imx274: add cropping support via SELECTION API Luca Ceresoli
2018-07-24 14:22   ` Sakari Ailus

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=201807140225.cKmtgIPL%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=leonl@leopardimaging.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=luca@lucaceresoli.net \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    /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).