From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [openeuler:openEuler-1.0-LTS 10307/22320] drivers/pinctrl/.tmp_pinctrl-ingenic.o: warning: objtool: ingenic_pinconf_set()+0x9c: sibling call from callable instruction with modified stack frame
Date: Thu, 9 May 2024 01:28:13 +0800 [thread overview]
Message-ID: <202405090152.efDVxQ9E-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "only Makefile file changed"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: kernel@openeuler.org
TO: Xie XiuQi <xiexiuqi@huawei.com>
tree: https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head: 9ff44822aad3feccdf9b76d1b04aa62e958c05e0
commit: 96d6a274fc187fff18c10499215920e011ddb46a [10307/22320] kbuild: add -fcf-protection=none when using retpoline flags
:::::: branch date: 6 hours ago
:::::: commit date: 4 years, 4 months ago
config: x86_64-buildonly-randconfig-005-20240508 (https://download.01.org/0day-ci/archive/20240509/202405090152.efDVxQ9E-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240509/202405090152.efDVxQ9E-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/r/202405090152.efDVxQ9E-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/pinctrl/.tmp_pinctrl-ingenic.o: warning: objtool: ingenic_pinconf_set()+0x9c: sibling call from callable instruction with modified stack frame
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-08 17:28 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=202405090152.efDVxQ9E-lkp@intel.com \
--to=lkp@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).