From: David Sterba <dsterba@suse•cz>
To: Naresh Kamboju <naresh.kamboju@linaro•org>
Cc: open list <linux-kernel@vger•kernel.org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
lkft-triage@lists•linaro.org, Qu Wenruo <wqu@suse•com>,
David Sterba <dsterba@suse•com>, Christoph Hellwig <hch@lst•de>,
Johannes Thumshirn <johannes.thumshirn@wdc•com>,
Filipe Manana <fdmanana@suse•com>, Arnd Bergmann <arnd@arndb•de>,
Stephen Rothwell <sfr@canb•auug.org.au>
Subject: Re: [next] ERROR: modpost: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!
Date: Tue, 12 Apr 2022 16:20:21 +0200 [thread overview]
Message-ID: <20220412142021.GX15609@suse.cz> (raw)
In-Reply-To: <CA+G9fYvXn1tgpESouPBwZgKnoeUNjM3CV1nzDWac6PjHqTskog@mail.gmail.com>
On Tue, Apr 12, 2022 at 05:28:08PM +0530, Naresh Kamboju wrote:
> Linux next-20220412 arm and i386 build failed due to below errors
> with kselftest merge configs.
>
> - build-arm-gcc-kselftest
> - build-i386-gcc-kselftest
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=i386
> CROSS_COMPILE=i686-linux-gnu- 'CC=sccache i686-linux-gnu-gcc'
> 'HOSTCC=sccache gcc'
>
> ERROR: modpost: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!
> make[2]: *** [/builds/linux/scripts/Makefile.modpost:134:
> modules-only.symvers] Error 1
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro•org>
The fixed patches are on the way and will appear in the next for-next
branch snapshot. Thanks.
prev parent reply other threads:[~2022-04-12 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 11:58 [next] ERROR: modpost: "__udivdi3" [fs/btrfs/btrfs.ko] undefined! Naresh Kamboju
2022-04-12 14:20 ` David Sterba [this message]
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=20220412142021.GX15609@suse.cz \
--to=dsterba@suse$(echo .)cz \
--cc=arnd@arndb$(echo .)de \
--cc=dsterba@suse$(echo .)com \
--cc=fdmanana@suse$(echo .)com \
--cc=hch@lst$(echo .)de \
--cc=johannes.thumshirn@wdc$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=wqu@suse$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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