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 10:44:26 +0200 [thread overview]
Message-ID: <87y2ducwlx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <606433e8-9626-09a8-2d1b-4a85065f91da@mind.be> (Arnout Vandecappelle's message of "Wed, 7 Apr 2021 09:32:47 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> 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?
> I applied it to next at the time, not to master, so I guess that was for a
> reason :-)
> I don't like putting this kind of risky changes on the stable branch. Since a
> follow-up patch was needed, it clearly was indeed risky. The first patch of that
> series was kind of a fix because it made sure that the wpa_supplicant build
> actually corresponds to the Buildroot configuration. The patch that introduced
> the CTRL_IFACE issue however was really a feature patch.
> So no, no backporting needed.
Ok, good.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-04-07 8:44 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
2021-04-07 7:32 ` Arnout Vandecappelle
2021-04-07 8:44 ` Peter Korsgaard [this message]
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=87y2ducwlx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox