From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] wpa-supplicant: add options to enable the new DBus interface
Date: Wed, 19 Sep 2012 21:56:33 +0200 [thread overview]
Message-ID: <505A2371.2000004@mind.be> (raw)
In-Reply-To: <1348049503-1469-2-git-send-email-s.neumann@raumfeld.com>
On 09/19/12 12:11, Sven Neumann wrote:
> Allow to configure the DBus interfaces that the wpa_supplicant
> binary should support (old or new or both). Also allow to
> enable introspection support on the new DBus interface.
>
> Signed-off-by: Sven Neumann<s.neumann@raumfeld.com>
> ---
> package/wpa_supplicant/Config.in | 19 ++++++++++++++
> package/wpa_supplicant/wpa_supplicant.mk | 42 ++++++++++++++++++++++++++----
> 2 files changed, 56 insertions(+), 5 deletions(-)
>
> diff --git a/package/wpa_supplicant/Config.in b/package/wpa_supplicant/Config.in
> index d7cefe3..95d9620 100644
> --- a/package/wpa_supplicant/Config.in
> +++ b/package/wpa_supplicant/Config.in
> @@ -30,6 +30,25 @@ config BR2_PACKAGE_WPA_SUPPLICANT_AP_SUPPORT
> (optionally, with WPS); this links in parts of hostapd functionality
> into wpa_supplicant.
>
> +config BR2_PACKAGE_WPA_SUPPLICANT_DBUS_OLD
> + bool "Enable support for old DBus control interface"
> + depends on BR2_PACKAGE_DBUS
> + help
> + Enable support for old DBus control interface
> + (fi.epitest.hostap.WPASupplicant).
> +
> +config BR2_PACKAGE_WPA_SUPPLICANT_DBUS_NEW
> + bool "Enable support for new DBus control interface"
> + depends on BR2_PACKAGE_DBUS
Still 8 spaces instead of 1 tab.
> + help
> + Enable support for new DBus control interface (fi.w1.wpa_supplicant1).
> +
> +config BR2_PACKAGE_WPA_SUPPLICANT_DBUS_INTROSPECTION
> + bool "Introspection support"
> + depends on BR2_PACKAGE_WPA_SUPPLICANT_DBUS_NEW
Still 8 spaces instead of 1 tab.
When I said the whitespace issue was the only thing had to be fixed, I didn't
mean that my other comments could be ignored :-)
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-09-19 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 8:34 [Buildroot] wpa-supplicant: add options to enable the new DBus interface Sven Neumann
2012-09-13 8:34 ` [Buildroot] [PATCH] " Sven Neumann
2012-09-18 22:04 ` Arnout Vandecappelle
2012-09-19 10:11 ` [Buildroot] wpa_supplicant changes Sven Neumann
2012-09-19 10:11 ` [Buildroot] [PATCH 1/3] wpa-supplicant: add options to enable the new DBus interface Sven Neumann
2012-09-19 19:56 ` Arnout Vandecappelle [this message]
2012-09-19 19:59 ` Arnout Vandecappelle
2012-09-19 10:11 ` [Buildroot] [PATCH 2/3] wpa_supplicant: remove redundant escaping from sed commands Sven Neumann
2012-09-19 20:06 ` Arnout Vandecappelle
2012-09-19 10:11 ` [Buildroot] [PATCH 3/3] wpa_supplicant: introduce macros for editing the .config file Sven Neumann
2012-09-19 20:33 ` Arnout Vandecappelle
[not found] ` <505810D1.8070806@essensium.com>
2012-09-19 9:02 ` [Buildroot] [PATCH] wpa-supplicant: add options to enable the new DBus interface Sven Neumann
2012-09-19 20:03 ` 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=505A2371.2000004@mind.be \
--to=arnout@mind.be \
--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