oe-kbuild-all.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: kernel test robot <lkp@intel.com>
Cc: "Ji-Ze Hong (Peter Hong)" <peter_hong@fintek.com.tw>,
	wg@grandegger.com, michal.swiatkowski@linux.intel.com,
	Steen.Hegelund@microchip.com, mailhol.vincent@wanadoo.fr,
	oe-kbuild-all@lists.linux.dev, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	frank.jungclaus@esd.eu, linux-kernel@vger.kernel.org,
	linux-can@vger.kernel.org, netdev@vger.kernel.org,
	hpeter+linux_kernel@gmail.com
Subject: Re: [PATCH V7] can: usb: f81604: add Fintek F81604 support
Date: Tue, 9 May 2023 14:14:51 +0200	[thread overview]
Message-ID: <20230509-exert-remindful-0c0e89bf6649-mkl@pengutronix.de> (raw)
In-Reply-To: <202305091802.pRFS6n2j-lkp@intel.com>

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

Good Bot!

On 09.05.2023 18:17:43, kernel test robot wrote:
> Hi Ji-Ze,
> 
> kernel test robot noticed the following build warnings:
> 
> [auto build test WARNING on mkl-can-next/testing]
> [also build test WARNING on linus/master v6.4-rc1 next-20230509]
> [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/Ji-Ze-Hong-Peter-Hong/can-usb-f81604-add-Fintek-F81604-support/20230509-154045
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git testing
> patch link:    https://lore.kernel.org/r/20230509073821.25289-1-peter_hong%40fintek.com.tw
> patch subject: [PATCH V7] can: usb: f81604: add Fintek F81604 support
> config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20230509/202305091802.pRFS6n2j-lkp@intel.com/config)
> compiler: sh4-linux-gcc (GCC) 12.1.0
> 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
>         # https://github.com/intel-lab-lkp/linux/commit/9549380f8d5eea359f8c83f48e10a0becfd13541
>         git remote add linux-review https://github.com/intel-lab-lkp/linux
>         git fetch --no-tags linux-review Ji-Ze-Hong-Peter-Hong/can-usb-f81604-add-Fintek-F81604-support/20230509-154045
>         git checkout 9549380f8d5eea359f8c83f48e10a0becfd13541
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sh olddefconfig
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=sh SHELL=/bin/bash drivers/net/
> 
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Link: https://lore.kernel.org/oe-kbuild-all/202305091802.pRFS6n2j-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>    drivers/net/can/usb/f81604.c: In function 'f81604_read_bulk_callback':
> >> drivers/net/can/usb/f81604.c:440:67: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'unsigned int' [-Wformat=]
>      440 |                 netdev_warn(netdev, "URB length %u not equal to %lu\n",
>          |                                                                 ~~^
>          |                                                                   |
>          |                                                                   long unsigned int
>          |                                                                 %u
>      441 |                             urb->actual_length, sizeof(*frame));
>          |                                                 ~~~~~~~~~~~~~~     
>          |                                                 |
>          |                                                 unsigned int

Replaced "%lu% by "%zu" while applying the patch.

Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde          |
Embedded Linux                   | https://www.pengutronix.de |
Vertretung Nürnberg              | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-9   |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-05-09 12:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230509073821.25289-1-peter_hong@fintek.com.tw>
2023-05-09 10:17 ` [PATCH V7] can: usb: f81604: add Fintek F81604 support kernel test robot
2023-05-09 12:14   ` Marc Kleine-Budde [this message]
2023-05-15  1:11     ` Peter Hong
2023-05-15  7:06       ` Marc Kleine-Budde
2023-05-10 10:54 ` 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=20230509-exert-remindful-0c0e89bf6649-mkl@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=Steen.Hegelund@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=frank.jungclaus@esd.eu \
    --cc=hpeter+linux_kernel@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=peter_hong@fintek.com.tw \
    --cc=wg@grandegger.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).