From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
Subject: drivers/regulator/mt6370-regulator.c:310:8-33: WARNING: Threaded IRQ with no primary handler requested without IRQF_ONESHOT (unless it is nested IRQ)
Date: Sat, 25 Mar 2023 07:05:33 +0800 [thread overview]
Message-ID: <202303250737.cy70MiLu-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: ChiYuan Huang <cy_huang@richtek.com>
CC: Lee Jones <lee@kernel.org>
CC: Andy Shevchenko <andy.shevchenko@gmail.com>
CC: ChiaEn Wu <chiaen_wu@richtek.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fd3d06ff5f4fa23f32bdb7f4d9f308503801d9e0
commit: b2adf788e6037cea0109313934f432f458190992 mfd: mt6370: Add MediaTek MT6370 support
date: 6 months ago
:::::: branch date: 2 hours ago
:::::: commit date: 6 months ago
config: sparc64-randconfig-c032-20230324 (https://download.01.org/0day-ci/archive/20230325/202303250737.cy70MiLu-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 12.1.0
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Reported-by: Julia Lawall <julia.lawall@inria.fr>
| Link: https://lore.kernel.org/r/202303250737.cy70MiLu-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> drivers/regulator/mt6370-regulator.c:310:8-33: WARNING: Threaded IRQ with no primary handler requested without IRQF_ONESHOT (unless it is nested IRQ)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-03-24 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 23:05 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-27 12:55 drivers/regulator/mt6370-regulator.c:310:8-33: WARNING: Threaded IRQ with no primary handler requested without IRQF_ONESHOT (unless it is nested IRQ) 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=202303250737.cy70MiLu-lkp@intel.com \
--to=lkp@intel.com \
--cc=julia.lawall@inria.fr \
--cc=oe-kbuild@lists.linux.dev \
/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 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.