mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: David Gow <davidgow@google.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Marie Zhussupova <marievic@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	KUnit Development <kunit-dev@googlegroups.com>,
	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: Mon, 25 Aug 2025 20:15:05 -0600	[thread overview]
Message-ID: <4d5bad8a-6afa-4284-8f78-b52e2cfedbf0@linuxfoundation.org> (raw)
In-Reply-To: <CABVgOSm2_FGfjQpUBttuUH5ZrMEqnaGkYVkN6N96wX7Qs8EE2Q@mail.gmail.com>

On 8/19/25 01:44, David Gow wrote:
> On Tue, 19 Aug 2025 at 00:32, Shuah Khan <skhan@linuxfoundation.org> wrote:
>>
>> On 8/17/25 20:08, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> After merging the kunit-next tree, today's linux-next build (x86_64
>>> allmodconfig) failed like this:
>>
>> Thank you Stephen. I did a allmodconfig build on 6.17-rc1 base - didn't
>> see the error.
>>
>> Marie, David, can you take a look this. Looks like conflict with drm
>> in next?
>>
> 
> Thanks, Shuah. I've managed to reproduce this with:
> ./tools/testing/kunit/kunit.py run --arch x86_64 --kunitconfig
> drivers/gpu/drm/xe
> 
> These patches fix it (and a corresponding drm/xe test failure):
> https://lore.kernel.org/linux-next/20250819073434.1411114-1-davidgow@google.com/T/#t
> 
> Ideally, they'll be squashed into the corresponding patches, as
> otherwise there'd be some temporary breakage during bisections. I can
> squash these into the original series and re-send it out if that works
> best for you.
> 

David,

Please squash them and resend - also I see a kernel test robot
error in patch 1/2.

I was going to squash them, but I saw the kernel test robot error patch.

thanks,
-- Shuah

  parent reply	other threads:[~2025-08-26  2:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18  2:08 Stephen Rothwell
2025-08-18 16:32 ` Shuah Khan
2025-08-19  7:44   ` David Gow
2025-08-25  6:05     ` Stephen Rothwell
2025-08-26  2:15     ` Shuah Khan [this message]
2025-08-26  9:24       ` David Gow
2025-08-27  5:49         ` Shuah Khan
2025-08-27  6:37           ` David Gow
  -- strict thread matches above, loose matches on Subject: below --
2024-10-04  4:11 Stephen Rothwell
2024-10-04 13:26 ` Gabriela Bittencourt
2024-10-04 18:36 ` Shuah Khan
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
2024-02-28  2:48 Stephen Rothwell
2024-02-28  3:26 ` 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=4d5bad8a-6afa-4284-8f78-b52e2cfedbf0@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=davidgow@google.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=marievic@google.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

Powered by JetHome