From: "José Pekkarinen" <jose.pekkarinen@unikie.com>
To: buildroot@buildroot.org
Cc: "José Pekkarinen" <jose.pekkarinen@unikie.com>
Subject: [Buildroot] [PATCH v2] package/wpa_supplicant: Allow mesh configuration
Date: Wed, 22 Sep 2021 14:38:20 +0300 [thread overview]
Message-ID: <20210922113820.3628-1-jose.pekkarinen@unikie.com> (raw)
wpa_supplicant defconfig doesn't enable CONFIG_MESH
by default, and currently there is only a path to
disable it in buildroot. This patch will restore
the logic to enable it.
Signed-off-by: José Pekkarinen <jose.pekkarinen@unikie.com>
---
[ v1 -> v2 ] s/CONFIG__MESH/CONFIG_MESH/
package/wpa_supplicant/wpa_supplicant.mk | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/package/wpa_supplicant/wpa_supplicant.mk b/package/wpa_supplicant/wpa_supplicant.mk
index e9078b9f89..3c0b0c1dfc 100644
--- a/package/wpa_supplicant/wpa_supplicant.mk
+++ b/package/wpa_supplicant/wpa_supplicant.mk
@@ -104,7 +104,9 @@ else
WPA_SUPPLICANT_CONFIG_DISABLE += CONFIG_WIFI_DISPLAY
endif
-ifeq ($(BR2_PACKAGE_WPA_SUPPLICANT_MESH_NETWORKING),)
+ifeq ($(BR2_PACKAGE_WPA_SUPPLICANT_MESH_NETWORKING),y)
+WPA_SUPPLICANT_CONFIG_ENABLE += CONFIG_MESH
+else
WPA_SUPPLICANT_CONFIG_DISABLE += CONFIG_MESH
endif
--
2.25.1
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-09-22 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 11:38 José Pekkarinen [this message]
2021-09-29 7:10 ` [Buildroot] [PATCH v2] package/wpa_supplicant: Allow mesh configuration José Pekkarinen
2021-09-29 8:37 ` Nicolas Cavallari
2021-10-06 6:28 ` José Pekkarinen
2021-10-06 19:21 ` Arnout Vandecappelle
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=20210922113820.3628-1-jose.pekkarinen@unikie.com \
--to=jose.pekkarinen@unikie.com \
--cc=buildroot@buildroot.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).