From: Johannes Berg <johannes@sipsolutions.net>
To: 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, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com, x86@kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: kunit alltests runs broken in mainline
Date: Mon, 25 Mar 2024 17:42:55 +0100 [thread overview]
Message-ID: <76b84bd180b3509dfcc1aba86836890ddd3fe3aa.camel@sipsolutions.net> (raw)
In-Reply-To: <7e2b745a-df07-41cb-a088-966aa46fc175@sirena.org.uk>
On Mon, 2024-03-25 at 16:23 +0000, Mark Brown wrote:
> On Mon, Mar 25, 2024 at 05:16:35PM +0100, Johannes Berg wrote:
>
> > Anyway, does it fix it for you as well? if yes, where/how should we get
> > that in?
>
> Seems to. Given the breakage I'd expect it to go to Linus urgently, I
> don't know that it super matters exactly how but I guess net will be
> sending a pull anyway and is the source of the breakage?
Hmm, yeah ... after the previous discussion I had just put the patch in
there directly in wireless, so I'll just add this fix too.
johannes
next prev parent reply other threads:[~2024-03-25 16:42 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 [this message]
2024-03-26 1:52 ` Jakub Kicinski
2024-03-26 7:55 ` Johannes Berg
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=76b84bd180b3509dfcc1aba86836890ddd3fe3aa.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=brendanhiggins@google.com \
--cc=broonie@kernel.org \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-wireless@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