From: Christian Melki <christian.melki@t2data.com>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] crda: update regdb version 2023.05.03 -> 2024.05.08
Date: Wed, 10 Jul 2024 13:41:07 +0200 [thread overview]
Message-ID: <c3f44237-bc90-4e7c-888e-152a8ff9de79@t2data.com> (raw)
In-Reply-To: <20240710105520.1030832-1-s.trumtrar@pengutronix.de>
Hi.
I was _just_ looking at my own update, this february, which never
was applied. Turned out I never sent it in. :)
Anyway, regdb was updated to 2024-07-04 a couple of days ago.
I was thinking if we're going to bump it, why not the latest?
Any chance you can do a new one with the latest release?
https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/log/
Regards,
Christian
On 7/10/24 12:55 PM, Steffen Trumtrar wrote:
> Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> ---
> rules/crda.make | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/rules/crda.make b/rules/crda.make
> index 0929e26da..b02649dc8 100644
> --- a/rules/crda.make
> +++ b/rules/crda.make
> @@ -26,8 +26,8 @@ CRDA_LICENSE_FILES := \
> file://LICENSE;md5=ef8b69b43141352d821fd66b64ff0ee7 \
> file://copyleft-next-0.3.0;md5=8743a2c359037d4d329a31e79eabeffe
>
> -CRDA_REGDB_VERSION := 2023.05.03
> -CRDA_REGDB_MD5 := 16009b1266a1d2ae5093e14b3eea7f05
> +CRDA_REGDB_VERSION := 2024.05.08
> +CRDA_REGDB_MD5 := 58c4f69d7bfe458f2cab4b3ddf816492
> CRDA_REGDB := wireless-regdb-$(CRDA_REGDB_VERSION)
> CRDA_REGDB_SUFFIX := tar.gz
> CRDA_REGDB_URL := \
next prev parent reply other threads:[~2024-07-10 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 10:55 Steffen Trumtrar
2024-07-10 11:41 ` Christian Melki [this message]
2024-07-10 12:51 ` Steffen Trumtrar
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=c3f44237-bc90-4e7c-888e-152a8ff9de79@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
--cc=s.trumtrar@pengutronix.de \
/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