Received-SPF: pass (google.com: domain of linux-wireless+bounces-3217-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Message-ID: <455bafff0d609eb182ba30a5fbf319888e0e961d.camel@sipsolutions.net>
Subject: Re: wireless-regdb key change broke crda tests after 37dcea0e6e5
From: Johannes Berg <johannes@sipsolutions.net>
To: Sergei Trofimovich <slyich@gmail.com>, linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org, Chen-Yu Tsai <wens@kernel.org>, Seth
	Forshee <sforshee@kernel.org>
Date: Tue, 06 Feb 2024 12:47:35 +0100
In-Reply-To: <ZcIXGjzrZrXPCBcp@nz.home>
References: <ZcIXGjzrZrXPCBcp@nz.home>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.50.3 (3.50.3-1.fc39) 
Precedence: bulk
MIME-Version: 1.0

Hi,

> "wireless-regdb: Update keys and maintainer information".
>=20
> Both `git` `master` version of `crda` and `wireless-regdb` still fail
> `crda`'s `make verify`.
>=20
> 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.

johannes