linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrey Ryabinin <ryabinin.a.a@gmail.com>,
	Brendan Higgins <brendanhiggins@google.com>
Subject: Re: linux-next: Tree for Sep 2 (lib/ubsan.c)
Date: Thu, 3 Sep 2020 23:12:01 -0700	[thread overview]
Message-ID: <fdf322d4-cc01-2c85-67cd-86b2d6f4ebff@infradead.org> (raw)
In-Reply-To: <3abfa193-a56e-66ba-1080-885906fa0196@infradead.org>

On 9/2/20 8:44 AM, Randy Dunlap wrote:
> On 9/2/20 1:09 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20200828:
>>
> 
> 
> on i386:
> 
> ../lib/ubsan.c: In function ‘ubsan_prologue’:
> ../lib/ubsan.c:141:2: error: implicit declaration of function ‘kunit_fail_current_test’; did you mean ‘kunit_init_test’? [-Werror=implicit-function-declaration]
>   kunit_fail_current_test();
> 
> 
> Full randconfig file is attached.
> 

Hi Brendan,

Do you know anything about this build error?

I can't find kunit_fail_current_test() anywhere.

thanks.
-- 
~Randy


  reply	other threads:[~2020-09-04  6:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  8:09 linux-next: Tree for Sep 2 Stephen Rothwell
2020-09-02 15:44 ` linux-next: Tree for Sep 2 (lib/ubsan.c) Randy Dunlap
2020-09-04  6:12   ` Randy Dunlap [this message]
2020-09-04  7:59     ` Brendan Higgins
2020-09-08 14:38       ` Randy Dunlap
2020-09-09  0:46         ` Stephen Rothwell
2020-09-09  0:49           ` Randy Dunlap
2020-09-09  0:55             ` Shuah Khan
2020-09-10  9:42               ` Brendan Higgins
2020-09-02 16:17 ` linux-next: Tree for Sep 2 (ip_tunnel, ip6_vti, sit, ip6_tunnel) Randy Dunlap

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=fdf322d4-cc01-2c85-67cd-86b2d6f4ebff@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=brendanhiggins@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ryabinin.a.a@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).