From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: drivers/pinctrl/cirrus/pinctrl-madera-core.o: warning: objtool: madera_pin_conf_set.cold()+0x4a: sibling call from callable instruction with modified stack frame
Date: Fri, 12 Jun 2020 05:19:12 +0800 [thread overview]
Message-ID: <202006120510.HiGKezjV%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 2dca74a40e1e7ff45079d85fc507769383039b9d
commit: 113d4bc9048336ba7c3d2ad972dbad4aef6e148a objtool: Fix clang switch table edge case
date: 4 months ago
config: x86_64-randconfig-a013-20200611 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce (this is a W=1 build):
git checkout 113d4bc9048336ba7c3d2ad972dbad4aef6e148a
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> drivers/pinctrl/cirrus/pinctrl-madera-core.o: warning: objtool: madera_pin_conf_set.cold()+0x4a: sibling call from callable instruction with modified stack frame
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 32702 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Borislav Petkov <bp@suse.de>
Subject: drivers/pinctrl/cirrus/pinctrl-madera-core.o: warning: objtool: madera_pin_conf_set.cold()+0x4a: sibling call from callable instruction with modified stack frame
Date: Fri, 12 Jun 2020 05:19:12 +0800 [thread overview]
Message-ID: <202006120510.HiGKezjV%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 2dca74a40e1e7ff45079d85fc507769383039b9d
commit: 113d4bc9048336ba7c3d2ad972dbad4aef6e148a objtool: Fix clang switch table edge case
date: 4 months ago
config: x86_64-randconfig-a013-20200611 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce (this is a W=1 build):
git checkout 113d4bc9048336ba7c3d2ad972dbad4aef6e148a
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> drivers/pinctrl/cirrus/pinctrl-madera-core.o: warning: objtool: madera_pin_conf_set.cold()+0x4a: sibling call from callable instruction with modified stack frame
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32702 bytes --]
next reply other threads:[~2020-06-11 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 21:19 kernel test robot [this message]
2020-06-11 21:19 ` drivers/pinctrl/cirrus/pinctrl-madera-core.o: warning: objtool: madera_pin_conf_set.cold()+0x4a: sibling call from callable instruction with modified stack frame 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=202006120510.HiGKezjV%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.