From: kernel test robot <lkp@intel.com>
To: lirongqing <lirongqing@baidu.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Sudeep Holla <Sudeep.Holla@arm.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Li RongQing <lirongqing@baidu.com>
Subject: Re: [PATCH] ACPI: processor: idle: Add __cpuidle to acpi_idle_lpi_enter
Date: Mon, 15 Jun 2026 19:40:33 +0800 [thread overview]
Message-ID: <202606151932.LNUR0wXJ-lkp@intel.com> (raw)
In-Reply-To: <20260615065401.4611-1-lirongqing@baidu.com>
Hi lirongqing,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on rafael-pm/bleeding-edge linus/master v7.1 next-20260612]
[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/lirongqing/ACPI-processor-idle-Add-__cpuidle-to-acpi_idle_lpi_enter/20260615-150110
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20260615065401.4611-1-lirongqing%40baidu.com
patch subject: [PATCH] ACPI: processor: idle: Add __cpuidle to acpi_idle_lpi_enter
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20260615/202606151932.LNUR0wXJ-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260615/202606151932.LNUR0wXJ-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/202606151932.LNUR0wXJ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> vmlinux.o: warning: objtool: acpi_idle_lpi_enter+0x28: call to acpi_processor_ffh_lpi_enter() leaves .noinstr.text section
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-06-15 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 6:54 [PATCH] ACPI: processor: idle: Add __cpuidle to acpi_idle_lpi_enter lirongqing
2026-06-15 11:40 ` kernel test robot [this message]
2026-06-15 19:44 ` 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=202606151932.LNUR0wXJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=Sudeep.Holla@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
/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