Content-Type: multipart/mixed; boundary="===============1812259142485364606==" MIME-Version: 1.0 From: Andy Shevchenko To: kbuild-all@lists.01.org Subject: Re: [PATCH v3] pinctrl: baytrail: Clear direct_irq_en flag on broken configs Date: Wed, 12 Jan 2022 22:44:33 +0200 Message-ID: In-Reply-To: List-Id: --===============1812259142485364606== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Wed, Jan 12, 2022 at 08:58:00PM +0100, Hans de Goede wrote: > On 1/8/22 19:54, kernel test robot wrote: > >>> drivers/pinctrl/intel/pinctrl-baytrail.c:1483:58: warning: format spe= cifies type 'long' but the argument has type 'int' [-Wformat] > > dev_dbg(vg->dev, "Pin %i: uses direct IRQ %ld\n", pi= n, match - direct_irq); > > ~~~ = ^~~~~~~~~~~~~~~~~~ > > %d > > include/linux/dev_printk.h:163:47: note: expanded from macro 'dev_db= g' > > dev_printk(KERN_DEBUG, dev, dev_fmt(fmt), ##__VA_ARG= S__); \ > > ~~~ ^~~~~~~~= ~~~ > > include/linux/dev_printk.h:129:34: note: expanded from macro 'dev_pr= intk' > > _dev_printk(level, dev, fmt, ##__VA_ARGS__); = \ > > ~~~ ^~~~~~~~~~~ > > 1 warning generated. > = > Hmm, ok. so x86_64 needs a %ld for the pointer arithmic result on i386 ne= eds a %d > without the 'l' what fun. I'll just store it in a temp int variable in th= e next > version. Why not to use uintptr_t and corresponding specifier (or ptrdiff_t)? -- = With Best Regards, Andy Shevchenko --===============1812259142485364606==--