All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] package/wpa_supplicant: handle CONFIG_CTRL_IFACE carefully
Date: Wed, 07 Apr 2021 09:22:55 +0200	[thread overview]
Message-ID: <87ft02eey8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <f768f65b-c4e3-89ea-60e7-37e1a68012bb@mind.be> (Arnout Vandecappelle's message of "Tue, 6 Apr 2021 22:10:59 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

Hi,

 >  To fix this, we can simply use "CONFIG_EAP_[A-Z0-9_]*" to disable all the EAP
 > options. I think EAP is the only one in that situation, but I haven't checked
 > all config options. There's also CONFIG_DPP that matches CONFIG_DPP2, but I
 > don't think that's actually intentional...

 >  So I think indeed the better solution is to change the patsubst lines.

 >  However, that's a much bigger change which requires a bit of testing and
 > double-checking (and deciding what to do with e.g. DPP2). So for now, I've
 > applied this patch, thanks. This patch can be backported to the stable branches.

We only added disabling logic post-2021.02, so it only affects master.

Should the disabling logic (and this patch) be backported to 2021.02.x?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2021-04-07  7:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16  2:18 [Buildroot] [PATCH 1/1] package/wpa_supplicant: fix WPA_SUPPLICANT_CONFIGURE_CMDS Tian Yuanhao
2021-03-16 10:02 ` Nicolas Cavallari
2021-03-17  3:37 ` [Buildroot] [PATCH v2 1/1] package/wpa_supplicant: fix wrong config Tian Yuanhao
2021-04-01  1:43   ` Tian Yuanhao
2021-04-02  9:08     ` Nicolas Cavallari
2021-04-03  2:23   ` [Buildroot] [PATCH v3 1/1] package/wpa_supplicant: handle CONFIG_CTRL_IFACE carefully Tian Yuanhao
2021-04-03  7:01     ` Yann E. MORIN
2021-04-03  7:49       ` Tian Yuanhao
2021-04-06 20:10         ` Arnout Vandecappelle
2021-04-07  7:22           ` Peter Korsgaard [this message]
2021-04-07  7:32             ` Arnout Vandecappelle
2021-04-07  8:44               ` Peter Korsgaard
2021-04-07 21:47           ` Yann E. MORIN

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=87ft02eey8.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.