From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: allow to build without CFG80211_REQUIRE_SIGNED_REGDB
Date: Mon, 13 Aug 2018 14:17:07 +0200 [thread overview]
Message-ID: <20180813121706.GB2153@redhat.com> (raw)
In-Reply-To: <1534160873.3093.9.camel@sipsolutions.net>
On Mon, Aug 13, 2018 at 01:47:53PM +0200, Johannes Berg wrote:
> Disagree, if anything should be changed, it should be changed to
>
> default y if !CERTIFICATION_ONUS
>
> but I prefer the way it works now, since it means setting certification
> onus won't immediately change this setting.
Ok, this works as supposed. Not sure why it did not work for me
before, maybe I just confused config options.
Regards
Stanislaw
prev parent reply other threads:[~2018-08-13 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 10:55 [PATCH] cfg80211: allow to build without CFG80211_REQUIRE_SIGNED_REGDB Stanislaw Gruszka
2018-08-13 10:09 ` Johannes Berg
2018-08-13 11:44 ` Stanislaw Gruszka
2018-08-13 11:47 ` Johannes Berg
2018-08-13 12:17 ` Stanislaw Gruszka [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=20180813121706.GB2153@redhat.com \
--to=sgruszka@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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).