From: kernel test robot <lkp@intel.com>
To: a <osalexandeko@gmail.com>, arnd@arndb.de, gregkh@linuxfoundation.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
a <a@js-host.myguest.virtualbox.org>,
Alex Kazansky <osalexandeko@gmail.com>
Subject: Re: [PATCH] [PATCH] drivers/misc: dummy-irq: use pr_* logging helpers
Date: Thu, 30 Apr 2026 11:06:44 +0800 [thread overview]
Message-ID: <202604301104.37n6lDbO-lkp@intel.com> (raw)
In-Reply-To: <20260419040308.4239-1-a@JS-Host.myguest.virtualbox.org>
Hi a,
kernel test robot noticed the following build warnings:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on char-misc/char-misc-next char-misc/char-misc-linus soc/for-next staging/staging-testing staging/staging-next staging/staging-linus linus/master v7.1-rc1 next-20260429]
[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/a/drivers-misc-dummy-irq-use-pr_-logging-helpers/20260426-190343
base: char-misc/char-misc-testing
patch link: https://lore.kernel.org/r/20260419040308.4239-1-a%40JS-Host.myguest.virtualbox.org
patch subject: [PATCH] [PATCH] drivers/misc: dummy-irq: use pr_* logging helpers
config: csky-randconfig-002-20260430 (https://download.01.org/0day-ci/archive/20260430/202604301104.37n6lDbO-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260430/202604301104.37n6lDbO-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202604301104.37n6lDbO-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/misc/dummy-irq.c:17:9: warning: "pr_fmt" redefined
17 | #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
| ^~~~~~
In file included from include/asm-generic/bug.h:31,
from arch/csky/include/asm/bug.h:18,
from include/linux/bug.h:5,
from include/linux/instrumented.h:10,
from include/linux/atomic/atomic-instrumented.h:17,
from include/linux/atomic.h:82,
from include/asm-generic/bitops/lock.h:5,
from arch/csky/include/asm/bitops.h:69,
from include/linux/bitops.h:67,
from include/linux/log2.h:12,
from include/asm-generic/div64.h:55,
from ./arch/csky/include/generated/asm/div64.h:1,
from include/linux/math.h:6,
from include/linux/math64.h:6,
from include/linux/time.h:6,
from include/linux/stat.h:19,
from include/linux/module.h:13,
from drivers/misc/dummy-irq.c:14:
include/linux/printk.h:401:9: note: this is the location of the previous definition
401 | #define pr_fmt(fmt) fmt
| ^~~~~~
vim +/pr_fmt +17 drivers/misc/dummy-irq.c
> 17 #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
18
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-04-30 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 4:03 [PATCH] [PATCH] drivers/misc: dummy-irq: use pr_* logging helpers a
2026-04-19 5:28 ` Greg KH
2026-04-30 3:06 ` kernel test robot [this message]
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=202604301104.37n6lDbO-lkp@intel.com \
--to=lkp@intel.com \
--cc=a@js-host.myguest.virtualbox.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=osalexandeko@gmail.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