From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] crda: install regulatory.db too
Date: Fri, 12 Mar 2021 08:33:05 +0100 [thread overview]
Message-ID: <20210312073305.GA306772@pengutronix.de> (raw)
In-Reply-To: <1e96ffe70635aa71c8bbf9b7849ecb8ba37465b7.camel@diehl.com>
Hi,
On Thu, Mar 11, 2021 at 07:55:21AM +0000, Denis Osterland-Heim wrote:
> Once more, sorry for the inconvenience.
No problem.
> Please find mbox attached.
You can just send the attached mbox. As you can see below, my email client
(mutt) quotes the attachment so I can easily reply and comment.
And I can apply the patch just like any inline patch, so no extra work for
me.
> Date: Thu, 11 Mar 2021 08:52:02 +0100
> From: Denis Osterland-Heim <denis.osterland@diehl.com>
> To: ptxdist@pengutronix.de
> Subject: [PATCH] crda: install regulatory.db too
> Message-ID: <20210311075202.1876-1-denis.osterland@diehl.com>
> X-Mailer: git-send-email 2.30.2
>
> Kernel >= 4.15 want to load this file.
>
> Signed-off-by: Denis Osterland-Heim <denis.osterland@diehl.com>
> ---
> rules/crda.make | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/rules/crda.make b/rules/crda.make
> index 724aa7ba9..9cbb7af93 100644
> --- a/rules/crda.make
> +++ b/rules/crda.make
> @@ -74,6 +74,10 @@ $(STATEDIR)/crda.install:
> @$(call world/install, CRDA)
> @install -vD -m 644 $(CRDA_REGDB_DIR)/$(CRDA_REGDB)/regulatory.bin \
> $(CRDA_PKGDIR)/usr/lib/crda/regulatory.bin
> + @install -vD -m 0644 $(CRDA_REGDB_DIR)/$(CRDA_REGDB)/regulatory.db \
> + $(CRDA_PKGDIR)/lib/firmware/regulatory.db
> + @install -vD -m 0644 $(CRDA_REGDB_DIR)/$(CRDA_REGDB)/regulatory.db.p7s \
> + $(CRDA_PKGDIR)/lib/firmware/regulatory.db.p7s
> @install -vD -m 644 $(CRDA_REGDB_DIR)/pubkeys/linville.key.pub.pem \
> $(CRDA_PKGDIR)/usr/lib/crda/pubkeys/linville.key.pub.pem
> @install -vD -m 644 $(CRDA_REGDB_DIR)/pubkeys/sforshee.key.pub.pem \
> @@ -103,6 +107,10 @@ $(STATEDIR)/crda.targetinstall:
> /usr/lib/crda/pubkeys)
> @$(call install_alternative, crda, 0, 0, 0644, \
> /usr/lib/crda/regulatory.bin)
> + @$(call install_alternative, crda, 0, 0, 0644, \
> + /lib/firmware/regulatory.db)
> + @$(call install_alternative, crda, 0, 0, 0644, \
> + /lib/firmware/regulatory.db.p7s)
So the commit message mentions regulatory.db but not regulatory.db.p7s.
What is that file for?
Michael
>
> @$(call install_finish, crda)
>
> --
> 2.30.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-03-12 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 7:53 Denis Osterland-Heim
2021-03-11 7:55 ` Denis Osterland-Heim
2021-03-12 7:33 ` Michael Olbrich [this message]
2021-03-12 9:08 ` Denis Osterland-Heim
2021-03-19 7:41 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20210312073305.GA306772@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@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