From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kalle Valo <kvalo@kernel.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
David Gow <davidgow@google.com>,
Brendan Higgins <brendanhiggins@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com
Subject: Re: pull-request: wireless-2024-01-22
Date: Tue, 23 Jan 2024 13:42:55 -0800 [thread overview]
Message-ID: <20240123134255.3eef6fd9@kernel.org> (raw)
In-Reply-To: <d4c1a7c715a1f47dc45c5d033822d8f47e304bd4.camel@sipsolutions.net>
On Tue, 23 Jan 2024 19:19:35 +0100 Johannes Berg wrote:
> Looks like that needs adjustments to the config file there, mostly? I
> can see about adding that, probably not that hard, at least for
> mac80211/cfg80211.
To be clear I was mostly thinking about mac80211/cfg80211...
> We're also adding unit tests to iwlwifi (slowly), any idea if we should
> enable that here also? It _is_ now possible to build PCI stuff on kunit,
> but it requires some additional config options (virt-pci etc.), not sure
> that's desirable here? It doesn't need it at runtime for the tests, of
> course.
but curious to hear about driver testing recommendations.
next prev parent reply other threads:[~2024-01-23 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 15:34 pull-request: wireless-2024-01-22 Kalle Valo
2024-01-23 16:45 ` Jakub Kicinski
2024-01-23 18:19 ` Johannes Berg
2024-01-23 18:22 ` Johannes Berg
2024-01-25 6:51 ` David Gow
2024-01-25 6:51 ` David Gow
2024-01-23 21:42 ` Jakub Kicinski [this message]
2024-01-23 22:06 ` Johannes Berg
2024-01-23 16:50 ` patchwork-bot+netdevbpf
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=20240123134255.3eef6fd9@kernel.org \
--to=kuba@kernel.org \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=johannes@sipsolutions.net \
--cc=kunit-dev@googlegroups.com \
--cc=kvalo@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.