From: Sergei Trofimovich <slyich@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
wireless-regdb@lists.infradead.org,
Chen-Yu Tsai <wens@kernel.org>,
Seth Forshee <sforshee@kernel.org>
Subject: Re: wireless-regdb key change broke crda tests after 37dcea0e6e5
Date: Tue, 6 Feb 2024 22:27:57 +0000 [thread overview]
Message-ID: <20240206222757.238a24f8@nz.home> (raw)
In-Reply-To: <455bafff0d609eb182ba30a5fbf319888e0e961d.camel@sipsolutions.net>
On Tue, 06 Feb 2024 12:47:35 +0100
Johannes Berg <johannes@sipsolutions.net> wrote:
> Hi,
>
> > "wireless-regdb: Update keys and maintainer information".
> >
> > Both `git` `master` version of `crda` and `wireless-regdb` still fail
> > `crda`'s `make verify`.
> >
> > Should `crda` key the key update as well?
>
> Maybe?
>
> But perhaps the real question is if you should still be shipping crda?
> It was last needed for kernel 4.15, and even the newest stable kernel
> based on or before it (4.14) is now EOL ...
>
> After that, we had the regdb loaded like a firmware file including the
> signatures, so the whole crda isn't needed any more.
Great point! `nixpkgs` uses `crda` only as a `hostapd` depend and
looking at modern `hostapd` it does not use it at all. I'll spend some
time removing it downstream. Thank you!
--
Sergei
next prev parent reply other threads:[~2024-02-07 5:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 11:25 wireless-regdb key change broke crda tests after 37dcea0e6e5 Sergei Trofimovich
2024-02-06 11:47 ` Johannes Berg
2024-02-06 22:27 ` Sergei Trofimovich [this message]
2024-02-07 7:58 ` Johannes Berg
2024-02-07 9:19 ` Kalle Valo
2024-02-07 9:22 ` 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=20240206222757.238a24f8@nz.home \
--to=slyich@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sforshee@kernel.org \
--cc=wens@kernel.org \
--cc=wireless-regdb@lists.infradead.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