From: Seth Forshee <seth.forshee@canonical.com>
To: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless-regdb: Do not hardcode 'sforshee' in the certificate commonName
Date: Wed, 17 Mar 2021 10:18:49 -0500 [thread overview]
Message-ID: <YFId2V808BExp/TH@ubuntu-x1> (raw)
In-Reply-To: <20210205180054.1031-1-nicolas.cavallari@green-communications.fr>
On Fri, Feb 05, 2021 at 07:00:54PM +0100, Nicolas Cavallari wrote:
> gen-pubcert.sh hardcodes the 'sforshee' common name when generating the
> certificate. Make it depend on REGDB_AUTHOR instead, which defaults to
> $(whoami).
>
> Signed-off-by: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
Applied, thanks!
prev parent reply other threads:[~2021-03-17 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 18:00 [PATCH] wireless-regdb: Do not hardcode 'sforshee' in the certificate commonName Nicolas Cavallari
2021-03-17 15:18 ` Seth Forshee [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=YFId2V808BExp/TH@ubuntu-x1 \
--to=seth.forshee@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nicolas.cavallari@green-communications.fr \
--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;
as well as URLs for NNTP newsgroup(s).