linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Brendan Higgins <brendanhiggins@google.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrey Ryabinin <ryabinin.a.a@gmail.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: linux-next: Tree for Sep 2 (lib/ubsan.c)
Date: Tue, 8 Sep 2020 18:55:44 -0600	[thread overview]
Message-ID: <90719242-ab0e-7bd9-1cce-5aac8940eb23@linuxfoundation.org> (raw)
In-Reply-To: <dea1bacd-48c2-067b-1bb2-00a0ee91196d@infradead.org>

On 9/8/20 6:49 PM, Randy Dunlap wrote:
> On 9/8/20 5:46 PM, Stephen Rothwell wrote:
>> Hi Randy,
>>
>> On Tue, 8 Sep 2020 07:38:31 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>>>
>>> On 9/4/20 12:59 AM, Brendan Higgins wrote:
>>>> On Thu, Sep 3, 2020 at 11:12 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>>>>>
>>>>> 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.
>>>>
>>>> Yeah, this got applied for some reason without the prerequisite
>>>> patches. It is from a two patch series, the other being here:
>>>>
>>>> https://lore.kernel.org/linux-kselftest/20200813205722.1384108-1-urielguajardojr@gmail.com/
>>>>
>>>> which in turn depends on another patchset which didn't make it into 5.9.
>>>>
>>>> Again, I don't know why this was applied without it's prereqs. Sorry about that.
>>>>    
>>>
>>> Well.  Who is responsible for this small mess?
>>> It is still killing linux-next builds for me (2020-0908).
>>
>> It came in via the kunit-next tree (Shuah cc'd).  I will revert commit
>> abe83f7621ee ("kunit: ubsan integration") today.
> 
> 

Sorry about that. I picked this up for 5.10 since it had the reviewed
by tags from Brendan.

I will drop this from kselftest kunit

thanks,
-- Shuah


  reply	other threads:[~2020-09-09  0:55 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
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 [this message]
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=90719242-ab0e-7bd9-1cce-5aac8940eb23@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=brendanhiggins@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.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).