Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Baptiste Theou <jtheou@adeneo-embedded.us>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] wpa-supplicant: Add NL80211 support option
Date: Thu, 7 Aug 2014 13:52:33 -0700	[thread overview]
Message-ID: <53E3E711.7000505@adeneo-embedded.us> (raw)
In-Reply-To: <53E3E37C.3080605@zacarias.com.ar>

HI,

Ok, please discard the patch.

IMHO, wpa_supplicant should provide the support of NL80211 by default 
('depends on BR2_PACKAGE_LIBNL) since it's the new standard.

I wasn't expected to have to select LIBNL manually.

Best regards,
On 08/07/2014 01:37 PM, Gustavo Zacarias wrote:
> On 08/07/2014 05:28 PM, Jean-Baptiste Theou wrote:
>
>> Signed-off-by: Jean-Baptiste Theou <jtheou@adeneo-embedded.us>
>> ---
>>   package/wpa_supplicant/Config.in         | 6 ++++++
>>   package/wpa_supplicant/wpa_supplicant.mk | 6 ++++++
>>   2 files changed, 12 insertions(+)
> Hi.
> Hmmm why?
> This is done automatically if the libnl package is selected/around.
> We really don't want to thread too thin into hostapd & wpa_supplicant
> config options.
> Regards.
>
>

-- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140807/d41578fa/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.jpg
Type: image/jpeg
Size: 8458 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140807/d41578fa/attachment.jpg>

  reply	other threads:[~2014-08-07 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 20:28 [Buildroot] [PATCH 1/1] wpa-supplicant: Add NL80211 support option Jean-Baptiste Theou
2014-08-07 20:37 ` Gustavo Zacarias
2014-08-07 20:52   ` Jean-Baptiste Theou [this message]
2014-08-08  8:41     ` Thomas Petazzoni
2014-08-08 16:16       ` Jean-Baptiste Theou
2014-08-08  8:38   ` Thomas Petazzoni

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=53E3E711.7000505@adeneo-embedded.us \
    --to=jtheou@adeneo-embedded.us \
    --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