Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] wpa_supplicant: Add NL80211 support option
Date: Sun, 12 Jul 2015 19:25:52 +0200	[thread overview]
Message-ID: <20150712192552.23e76408@free-electrons.com> (raw)
In-Reply-To: <1407514672-6231-1-git-send-email-jtheou@adeneo-embedded.us>

Dear Jean-Baptiste Theou,

On Fri, 8 Aug 2014 09:17:52 -0700, Jean-Baptiste Theou wrote:
> When you select wpa_supplicant, having an visual indication about the
> support or not of NL80211 is important.
> 
> And even if libnl is available, you may want to disable the support of
> NL80211 inside wpa_supplicant.

You forgot your Signed-off-by here. But we anyway have more comments
below.

> +config BR2_PACKAGE_WPA_SUPPLICANT_NL80211
> +	bool "Enable NL80211"
> +	default y if BR2_PACKAGE_LIBNL
> +	select BR2_PACKAGE_LIBNL
> +	help
> +	  Enable support for NL80211.

In which cases would you want to *not* have NL80211 support if you
already have libnl enabled? What is the reason/use-case?

If the NL80211 support in wpa_supplicant itself adds a significant
binary size to the filesystem, then it might be useful to have an
option such as the one you propose. But in this case, you should
include some numbers in your commit log.

Also, your patch keeps the automatic dependency handling of libnl, and
adds explicitly dependency handling on top of it, which doesn't make a
lot of sense: it should really be either one or the other solution, not
both.

You can also see slide 146 and following of
http://free-electrons.com/doc/training/buildroot/buildroot-slides.pdf
for more details about automatic or explicit handling of optional
dependencies.

In the mean time, we'll mark your patch as Rejected in patchwork. Don't
hesitate to resubmit a patch with a better explanation, and a cleanup
of automatic vs. explicit handling of the libnl dependency.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-07-12 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 16:17 [Buildroot] [PATCH v2] wpa_supplicant: Add NL80211 support option Jean-Baptiste Theou
2015-07-12 17:25 ` Thomas Petazzoni [this message]
2015-07-13  9:24   ` Nicolas Cavallari
2015-07-13  9:29     ` Thomas Petazzoni
2015-07-16 13:02       ` [Buildroot] [PATCH 1/2] wpa_supplicant: Add an explicit option to enable nl80211 Nicolas Cavallari
2015-07-16 13:02         ` [Buildroot] [PATCH 2/2] wpa_supplicant: Have Hotspot 2.0 depend on nl80211 Nicolas Cavallari
2015-07-17  6:41           ` Baruch Siach
2015-07-17  7:45             ` Thomas Petazzoni
2015-07-17  8:00               ` Nicolas Cavallari
2015-07-17 10:00               ` Baruch Siach
2015-07-17  6:39         ` [Buildroot] [PATCH 1/2] wpa_supplicant: Add an explicit option to enable nl80211 Baruch Siach
2015-07-17  7:49           ` Nicolas Cavallari
2015-07-17  7:59             ` [Buildroot] [PATCH 1/2 v2] " Nicolas Cavallari
2015-07-17  7:59               ` [Buildroot] [PATCH 2/2 v2] wpa_supplicant: Have Hotspot 2.0 depend on nl80211 Nicolas Cavallari
2015-09-17 15:31                 ` [Buildroot] [2/2, " Gary Bisson
2015-09-17 17:21                   ` Nicolas Cavallari
2016-01-10 13:10                     ` Yann E. MORIN
2015-09-17 15:26               ` [Buildroot] [1/2, v2] wpa_supplicant: Add an explicit option to enable nl80211 Gary Bisson
2015-10-11 12:47         ` [Buildroot] [PATCH 1/2] " 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=20150712192552.23e76408@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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