From: Johannes Berg <johannes@sipsolutions.net>
To: Shuah Khan <skhan@linuxfoundation.org>,
David Gow <davidgow@google.com>, SeongJae Park <sj@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>, Mark Brown <broonie@kernel.org>,
Brendan Higgins <brendanhiggins@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: Thu, 28 Mar 2024 23:11:55 +0100 [thread overview]
Message-ID: <eccb00604d9dae9b67d3d97d0526eb53cd6ffca7.camel@sipsolutions.net> (raw)
In-Reply-To: <6591ea0d-572b-4deb-b2a7-da58ed91c8f9@linuxfoundation.org>
On Thu, 2024-03-28 at 14:08 -0600, Shuah Khan wrote:
> On 3/26/24 04:09, David Gow wrote:
> > On Tue, 26 Mar 2024 at 15:55, Johannes Berg <johannes@sipsolutions.net> wrote:
> > >
> > > 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.
>
> You are welcome to send this with wireless pull if you like
> or I can include it in my pull request.
It's already in net now, and in the pull request to Linus here:
https://lore.kernel.org/netdev/20240328143117.26574-1-pabeni@redhat.com
johannes
prev parent reply other threads:[~2024-03-28 22:11 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
2024-03-26 10:09 ` David Gow
2024-03-28 20:08 ` Shuah Khan
2024-03-28 22:11 ` Johannes Berg [this message]
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=eccb00604d9dae9b67d3d97d0526eb53cd6ffca7.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=sj@kernel.org \
--cc=skhan@linuxfoundation.org \
--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