From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [morimoto-linux:fw-cleanup-2020-12-08-v1 65/70] /tmp/ccZoOXuM.s:82: Error: symbol `__kstrtab_snd_soc_dai_set_fmt' is already defined
Date: Tue, 08 Dec 2020 16:00:05 +0800 [thread overview]
Message-ID: <202012081601.teSFWT2E-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
tree: https://github.com/morimoto/linux fw-cleanup-2020-12-08-v1
head: 7bec55c91dcc40e561497938a4b24aff3b8b51ba
commit: 4001492eb32d2203f7f157d4991db7496d6b628d [65/70] ASoC: add snd_soc_runtime_get_dai_fmt()
config: i386-randconfig-c001-20201208 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/morimoto/linux/commit/4001492eb32d2203f7f157d4991db7496d6b628d
git remote add morimoto-linux https://github.com/morimoto/linux
git fetch --no-tags morimoto-linux fw-cleanup-2020-12-08-v1
git checkout 4001492eb32d2203f7f157d4991db7496d6b628d
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
/tmp/ccZoOXuM.s: Assembler messages:
>> /tmp/ccZoOXuM.s:82: Error: symbol `__kstrtab_snd_soc_dai_set_fmt' is already defined
>> /tmp/ccZoOXuM.s:84: Error: symbol `__kstrtabns_snd_soc_dai_set_fmt' is already defined
/tmp/ccZoOXuM.s:90: Error: symbol `__ksymtab_snd_soc_dai_set_fmt' is already defined
---
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: 34992 bytes --]
reply other threads:[~2020-12-08 8:00 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=202012081601.teSFWT2E-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.