From: Johannes Berg <johannes@sipsolutions.net>
To: Jakub Kicinski <kuba@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: Brendan Higgins <brendanhiggins@google.com>,
David Gow <davidgow@google.com>, Rae Moar <rmoar@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"kunit-dev@googlegroups.com" <kunit-dev@googlegroups.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: kunit alltests runs broken in mainline
Date: Tue, 26 Mar 2024 08:55:12 +0100 [thread overview]
Message-ID: <33670310a2b84d1a650b2aa087ac9657fa4abf84.camel@sipsolutions.net> (raw)
In-Reply-To: <20240325185235.2f704004@kernel.org>
On Tue, 2024-03-26 at 01:52 +0000, Jakub Kicinski wrote:
>
> I'm late to the party, but FWIW I had to toss this into netdev testing
> tree as a local patch:
>
> CONFIG_NETDEVICES=y
> CONFIG_WLAN=y
I'll send this in the next wireless pull, soon.
> CONFIG_DAMON_DBGFS_DEPRECATED=y
> The DAMON config was also breaking UML for us, BTW, and I don't see
> any fix for that in Linus's tree. Strangeness.
I noticed that too (though didn't actually find the fix) against net-
next, wireless trees are still a bit behind. I guess it'll get fixed
eventually.
johannes
next prev parent reply other threads:[~2024-03-26 7:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 15:21 kunit alltests runs broken in mainline Mark Brown
2024-03-25 15:29 ` Johannes Berg
2024-03-25 15:55 ` Mark Brown
2024-03-25 16:16 ` Johannes Berg
2024-03-25 16:23 ` Mark Brown
2024-03-25 16:42 ` Johannes Berg
2024-03-26 1:52 ` Jakub Kicinski
2024-03-26 7:55 ` Johannes Berg [this message]
2024-03-26 10:09 ` David Gow
2024-03-28 20:08 ` Shuah Khan
2024-03-28 22:11 ` Johannes Berg
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=33670310a2b84d1a650b2aa087ac9657fa4abf84.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=brendanhiggins@google.com \
--cc=broonie@kernel.org \
--cc=davidgow@google.com \
--cc=kuba@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmoar@google.com \
--cc=x86@kernel.org \
/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