From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] wireless-regdb: Update to 2022-08-12
Date: Sun, 18 Sep 2022 11:09:11 +0200 [thread overview]
Message-ID: <FF3283DB-1879-4740-848D-4F20630073BB@ipfire.org> (raw)
In-Reply-To: <d0753c64-ddc9-dd1b-7dcf-69a3322d3bac@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 17 Sep 2022, at 18:50, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> No changelog is provided, please refer to
> https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/log/
> for the commits since 2022-02-18.
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> lfs/wireless-regdb | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/lfs/wireless-regdb b/lfs/wireless-regdb
> index 640651102..0401f460c 100644
> --- a/lfs/wireless-regdb
> +++ b/lfs/wireless-regdb
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2021 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2022 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -24,10 +24,10 @@
>
> include Config
>
> -VER = 2022.02.18
> +VER = 2022-08-12
>
> -THISAPP = wireless-regdb-$(VER)
> -DL_FILE = $(THISAPP).tar.xz
> +THISAPP = wireless-regdb-master-$(VER)
> +DL_FILE = $(THISAPP).tar.gz
> DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
>
> @@ -41,7 +41,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 1237537a5d9ed249cc53b838b65effa83ceecd06bb76b11388a6c7673cd61322026617f033bea53d024f15a58ca19c4ab51bb624f2ee8fb1f2233b8e99140d4a
> +$(DL_FILE)_BLAKE2 = 9459dbc568266d71a4a6dabb6c0478d7ec9998fd839428b394b66cced64f77f302d01295170ca7e141fb9bfc2467a43f2c0ca2d23687a996ae24d2cecf166039
>
> install : $(TARGET)
>
> @@ -70,7 +70,7 @@ $(subst %,%_BLAKE2,$(objects)) :
>
> $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> @$(PREBUILD)
> - @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE)
> + @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar xzf $(DIR_DL)/$(DL_FILE)
> cd $(DIR_APP) && make install
> cp -vf $(DIR_APP)/db.txt /lib/firmware/regulatorydb.txt
> @rm -rf $(DIR_APP)
> --
> 2.35.3
prev parent reply other threads:[~2022-09-18 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 16:50 Peter Müller
2022-09-17 21:14 ` Adolf Belka
2022-09-18 9:09 ` Michael Tremer [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=FF3283DB-1879-4740-848D-4F20630073BB@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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