From: kernel test robot <lkp@intel.com>
To: Prathamesh Shete <pshete@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jon Hunter <jonathanh@nvidia.com>,
Petlozu Pravareshwar <petlozup@nvidia.com>
Subject: [jonhunter:tegra/next-fixes 4/6] Warning: drivers/soc/tegra/pmc.c:477 struct member 'pending_wake_status' not described in 'tegra_pmc'
Date: Thu, 15 Jan 2026 22:00:50 +0800 [thread overview]
Message-ID: <202601152118.iUDaBhog-lkp@intel.com> (raw)
tree: https://github.com/jonhunter/linux tegra/next-fixes
head: 8db7df69105098e025ef2c558d2a3e23bc788a9b
commit: 8c40b13eff0e1a7d46a38648951ff0b9581c0628 [4/6] soc/tegra: pmc: Fix unsafe generic_handle_irq() call
config: arm-randconfig-002-20260115 (https://download.01.org/0day-ci/archive/20260115/202601152118.iUDaBhog-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9b8addffa70cee5b2acc5454712d9cf78ce45710)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260115/202601152118.iUDaBhog-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/202601152118.iUDaBhog-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/soc/tegra/pmc.c:477 struct member 'pending_wake_status' not described in 'tegra_pmc'
>> Warning: drivers/soc/tegra/pmc.c:477 struct member 'pending_wake_irq_work' not described in 'tegra_pmc'
>> Warning: drivers/soc/tegra/pmc.c:477 struct member 'pending_wake_status' not described in 'tegra_pmc'
>> Warning: drivers/soc/tegra/pmc.c:477 struct member 'pending_wake_irq_work' not described in 'tegra_pmc'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-15 14:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202601152118.iUDaBhog-lkp@intel.com \
--to=lkp@intel.com \
--cc=jonathanh@nvidia.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=petlozup@nvidia.com \
--cc=pshete@nvidia.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 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.