From: Shuah Khan <skhan@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Brendan Higgins <brendanhiggins@google.com>
Cc: David Gow <davidgow@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: linux-next: build failure after merge of the kunit-next tree
Date: Tue, 27 Feb 2024 20:26:55 -0700 [thread overview]
Message-ID: <4eb24c55-6a8b-49bb-a54a-59f00b05b3a0@linuxfoundation.org> (raw)
In-Reply-To: <20240228134818.7b6134dc@canb.auug.org.au>
On 2/27/24 19:48, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kunit-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> Caused by commit
>
> e00c5a9fa617 ("kunit: Annotate _MSG assertion variants with gnu printf specifiers")
>
> Please fix all the current problems before applying a patch to warn
> about them.
>
> I have used the kunit-next tree from next-20240227 for today.
This is my bad. I should have dropped this patch when I couldn't
apply the patch that fixed the drivers/gpu/drm/tests/drm_buddy_test.c
It is fixed now. I dropped the problem commit
e00c5a9fa617 ("kunit: Annotate _MSG assertion variants with gnu printf specifiers")
thanks,
-- Shuah
next prev parent reply other threads:[~2024-02-28 3:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 2:48 linux-next: build failure after merge of the kunit-next tree Stephen Rothwell
2024-02-28 3:26 ` Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-29 4:26 Stephen Rothwell
2024-02-29 15:07 ` Shuah Khan
2024-03-01 7:15 ` David Gow
2024-03-01 10:43 ` Stephen Rothwell
2024-03-01 16:05 ` Shuah Khan
2024-03-01 20:46 ` Stephen Rothwell
2024-03-01 22:30 ` Shuah Khan
2024-03-06 15:25 ` Shuah Khan
2020-01-16 5:57 Stephen Rothwell
2020-01-16 11:23 ` Alan Maguire
2020-01-16 23:27 ` Rafael J. Wysocki
2020-01-10 6:43 Stephen Rothwell
2020-01-10 11:56 ` Alan Maguire
2020-01-13 21:11 ` Brendan Higgins
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=4eb24c55-6a8b-49bb-a54a-59f00b05b3a0@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).