From: Andy Shevchenko <andriy.shevchenko@intel.com> To: Hans de Goede <hdegoede@redhat.com> Cc: kernel test robot <lkp@intel.com>, Mika Westerberg <mika.westerberg@linux.intel.com>, Andy Shevchenko <andy@kernel.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com>, Linus Walleij <linus.walleij@linaro.org>, llvm@lists.linux.dev, kbuild-all@lists.01.org, linux-gpio@vger.kernel.org Subject: Re: [PATCH v3] pinctrl: baytrail: Clear direct_irq_en flag on broken configs Date: Wed, 12 Jan 2022 22:44:33 +0200 [thread overview] Message-ID: <Yd89sQz8L/KJ4BXA@smile.fi.intel.com> (raw) In-Reply-To: <eb4ef470-cfaf-13be-cb66-ca38c1a85a23@redhat.com> 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 specifies type 'long' but the argument has type 'int' [-Wformat] > > dev_dbg(vg->dev, "Pin %i: uses direct IRQ %ld\n", pin, match - direct_irq); > > ~~~ ^~~~~~~~~~~~~~~~~~ > > %d > > include/linux/dev_printk.h:163:47: note: expanded from macro 'dev_dbg' > > dev_printk(KERN_DEBUG, dev, dev_fmt(fmt), ##__VA_ARGS__); \ > > ~~~ ^~~~~~~~~~~ > > include/linux/dev_printk.h:129:34: note: expanded from macro 'dev_printk' > > _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 needs a %d > without the 'l' what fun. I'll just store it in a temp int variable in the next > version. Why not to use uintptr_t and corresponding specifier (or ptrdiff_t)? -- With Best Regards, Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@intel.com> 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 [thread overview] Message-ID: <Yd89sQz8L/KJ4BXA@smile.fi.intel.com> (raw) In-Reply-To: <eb4ef470-cfaf-13be-cb66-ca38c1a85a23@redhat.com> [-- Attachment #1: Type: text/plain, Size: 1321 bytes --] 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 specifies type 'long' but the argument has type 'int' [-Wformat] > > dev_dbg(vg->dev, "Pin %i: uses direct IRQ %ld\n", pin, match - direct_irq); > > ~~~ ^~~~~~~~~~~~~~~~~~ > > %d > > include/linux/dev_printk.h:163:47: note: expanded from macro 'dev_dbg' > > dev_printk(KERN_DEBUG, dev, dev_fmt(fmt), ##__VA_ARGS__); \ > > ~~~ ^~~~~~~~~~~ > > include/linux/dev_printk.h:129:34: note: expanded from macro 'dev_printk' > > _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 needs a %d > without the 'l' what fun. I'll just store it in a temp int variable in the next > version. Why not to use uintptr_t and corresponding specifier (or ptrdiff_t)? -- With Best Regards, Andy Shevchenko
next prev parent reply other threads:[~2022-01-12 20:45 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-07 23:44 [PATCH v3] pinctrl: baytrail: Clear direct_irq_en flag on broken configs Hans de Goede [not found] ` <CAHp75Vfgpm7sROw_Ay8+tK0bhu-kCbS=O_kwax+i_vaH7H4wXA@mail.gmail.com> 2022-01-08 9:59 ` [PATCH] " Hans de Goede 2022-01-12 20:20 ` Hans de Goede 2022-01-12 20:42 ` Andy Shevchenko 2022-01-12 20:45 ` Hans de Goede 2022-01-08 18:54 ` [PATCH v3] " kernel test robot 2022-01-08 18:54 ` kernel test robot 2022-01-12 19:58 ` Hans de Goede 2022-01-12 19:58 ` Hans de Goede 2022-01-12 20:44 ` Andy Shevchenko [this message] 2022-01-12 20:44 ` Andy Shevchenko 2022-01-12 20:50 ` Hans de Goede 2022-01-12 20:50 ` Hans de Goede 2022-01-12 21:01 ` Andy Shevchenko 2022-01-12 21:01 ` Andy Shevchenko 2022-01-08 18:54 ` kernel test robot 2022-01-08 18: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=Yd89sQz8L/KJ4BXA@smile.fi.intel.com \ --to=andriy.shevchenko@intel.com \ --cc=andy@kernel.org \ --cc=bgolaszewski@baylibre.com \ --cc=hdegoede@redhat.com \ --cc=kbuild-all@lists.01.org \ --cc=linus.walleij@linaro.org \ --cc=linux-gpio@vger.kernel.org \ --cc=lkp@intel.com \ --cc=llvm@lists.linux.dev \ --cc=mika.westerberg@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.