mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Chenwandun <chenwandun@huawei.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Dave Airlie <airlied@redhat.com>, Lyude Paul <lyude@redhat.com>
Subject: stacktrace.c:undefined reference to `save_stack_trace'
Date: Wed, 4 Dec 2019 21:41:09 +0800	[thread overview]
Message-ID: <201912042108.h2x78058%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

Hi Chenwandun,

It's probably a bug fix that unveils the link errors.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   63de37476ebd1e9bab6a9e17186dc5aa1da9ea99
commit: 68acde7629d75d460760a3124c52f358eecc6d26 drm/dp_mst: fix gcc compile error
date:   4 weeks ago
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 68acde7629d75d460760a3124c52f358eecc6d26
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=m68k 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   kernel/stacktrace.o: In function `stack_trace_save':
>> stacktrace.c:(.text+0x120): undefined reference to `save_stack_trace'

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 51360 bytes --]

             reply	other threads:[~2019-12-04 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 13:41 kbuild test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-01  6:18 kbuild test robot
2019-11-30  9:31 kbuild 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=201912042108.h2x78058%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=airlied@redhat.com \
    --cc=chenwandun@huawei.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyude@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®