From: kbuild test robot <lkp@intel.com>
To: Chenwandun <chenwandun@huawei.com>
Cc: Dave Airlie <airlied@redhat.com>,
intel-gfx@lists.freedesktop.org, kbuild-all@lists.01.org,
dri-devel@lists.freedesktop.org
Subject: [drm-tip:drm-tip 1865/1875] stacktrace.c:undefined reference to `save_stack_trace'
Date: Wed, 6 Nov 2019 12:19:59 +0800 [thread overview]
Message-ID: <201911061256.IgBY8qrw%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
Hi Chenwandun,
It's probably a bug fix that unveils the link errors.
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: f5cfd96ad87b58bf3b5dfa5365f8beb8bac15a38
commit: 68acde7629d75d460760a3124c52f358eecc6d26 [1865/1875] drm/dp_mst: fix gcc compile error
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/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 51354 bytes --]
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Chenwandun <chenwandun@huawei.com>
Cc: Dave Airlie <airlied@redhat.com>,
intel-gfx@lists.freedesktop.org, kbuild-all@lists.01.org,
dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [drm-tip:drm-tip 1865/1875] stacktrace.c:undefined reference to `save_stack_trace'
Date: Wed, 6 Nov 2019 12:19:59 +0800 [thread overview]
Message-ID: <201911061256.IgBY8qrw%lkp@intel.com> (raw)
Message-ID: <20191106041959.4jklJIf7mrj8ti6Dsv8AaqXfOHHXs0EpcMV0-PyyIfI@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
Hi Chenwandun,
It's probably a bug fix that unveils the link errors.
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: f5cfd96ad87b58bf3b5dfa5365f8beb8bac15a38
commit: 68acde7629d75d460760a3124c52f358eecc6d26 [1865/1875] drm/dp_mst: fix gcc compile error
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/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 51354 bytes --]
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-11-06 4:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 4:19 kbuild test robot [this message]
2019-11-06 4:19 ` [Intel-gfx] [drm-tip:drm-tip 1865/1875] stacktrace.c:undefined reference to `save_stack_trace' 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=201911061256.IgBY8qrw%lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@redhat.com \
--cc=chenwandun@huawei.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox