From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Mark Brown <broonie@kernel.org>, kernel test robot <lkp@intel.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: FAILED: load BTF from vmlinux: No such file or directory
Date: Fri, 4 Nov 2022 16:23:01 +0800 [thread overview]
Message-ID: <80c8a969-b88c-fec3-ac32-0a61295decd6@intel.com> (raw)
In-Reply-To: <Y2Lig+5ak3zKuPa1@sirena.org.uk>
On 11/3/2022 5:34 AM, Mark Brown wrote:
> On Thu, Nov 03, 2022 at 05:27:38AM +0800, kernel test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: 8e5423e991e8cd0988d0c4a3f4ac4ca1af7d148a
>> commit: 4e8ff35878685291978b93543d6b9e9290be770a ASoC: codecs: tlv320adc3xxx: Wrap adc3xxx_i2c_remove() in __exit_p()
>> date: 2 weeks ago
>> config: arc-buildonly-randconfig-r004-20221103
>> compiler: arceb-elf-gcc (GCC) 12.1.0
>
> ...
>
>> All errors (new ones prefixed by >>):
>>
>> Complex, interval and imaginary float types are not supported
>> Encountered error while encoding BTF.
>>>> FAILED: load BTF from vmlinux: No such file or directory
>
> This looks very much like a false positive, it is difficult to
> understand how a change such as the one identified could trigger such an
> issue.
>
Hi Mark,
Sorry for the noise, it's a false positive, the commit here fixed a
error and let the build process continuing which let the bot thought
the new error is from this commit.
Best Regards,
Rong Chen
prev parent reply other threads:[~2022-11-04 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 21:27 kernel test robot
2022-11-02 21:34 ` Mark Brown
2022-11-04 8:23 ` Chen, Rong A [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=80c8a969-b88c-fec3-ac32-0a61295decd6@intel.com \
--to=rong.a.chen@intel.com \
--cc=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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®