From: David Sterba <dsterba@suse.cz>
To: kernel test robot <lkp@intel.com>
Cc: Josef Bacik <josef@toxicpanda.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
David Sterba <dsterba@suse.com>
Subject: Re: disk-io.c:undefined reference to `atomic64_set_386'
Date: Tue, 6 Apr 2021 16:43:03 +0200 [thread overview]
Message-ID: <20210406144303.GF7604@suse.cz> (raw)
In-Reply-To: <202104010035.c4LXmhAY-lkp@intel.com>
On Thu, Apr 01, 2021 at 12:34:38AM +0800, kernel test robot wrote:
> Hi Josef,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 5e46d1b78a03d52306f21f77a4e4a144b6d31486
> commit: 8260edba67a2e6bd5e709d32188e23aa22cb4a38 btrfs: make the init of static elements in fs_info separate
> date: 1 year ago
> config: um-randconfig-r023-20210330 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8260edba67a2e6bd5e709d32188e23aa22cb4a38
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 8260edba67a2e6bd5e709d32188e23aa22cb4a38
> # save the attached .config to linux build tree
> make W=1 ARCH=um
All the reports regarding atomic64_*_386 are from ARCH=um build, so
it needs to be fixed there.
WARNING: multiple messages have this Message-ID (diff)
From: David Sterba <dsterba@suse.cz>
To: kbuild-all@lists.01.org
Subject: Re: disk-io.c:undefined reference to `atomic64_set_386'
Date: Tue, 06 Apr 2021 16:43:03 +0200 [thread overview]
Message-ID: <20210406144303.GF7604@suse.cz> (raw)
In-Reply-To: <202104010035.c4LXmhAY-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
On Thu, Apr 01, 2021 at 12:34:38AM +0800, kernel test robot wrote:
> Hi Josef,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 5e46d1b78a03d52306f21f77a4e4a144b6d31486
> commit: 8260edba67a2e6bd5e709d32188e23aa22cb4a38 btrfs: make the init of static elements in fs_info separate
> date: 1 year ago
> config: um-randconfig-r023-20210330 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8260edba67a2e6bd5e709d32188e23aa22cb4a38
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 8260edba67a2e6bd5e709d32188e23aa22cb4a38
> # save the attached .config to linux build tree
> make W=1 ARCH=um
All the reports regarding atomic64_*_386 are from ARCH=um build, so
it needs to be fixed there.
next prev parent reply other threads:[~2021-04-06 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 16:34 disk-io.c:undefined reference to `atomic64_set_386' kernel test robot
2021-03-31 16:34 ` kernel test robot
2021-04-06 14:43 ` David Sterba [this message]
2021-04-06 14:43 ` David Sterba
2021-04-06 16:12 ` Randy Dunlap
2021-04-06 16:12 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2021-03-31 2:09 kernel test robot
2021-03-31 2:09 ` 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=20210406144303.GF7604@suse.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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 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.