Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] optional DBus support in wpa_supplicant
Date: Mon, 13 Jul 2009 12:05:42 -0300	[thread overview]
Message-ID: <4A5B4D46.6010807@zacarias.com.ar> (raw)
In-Reply-To: <1247495564.20117.4.camel@sven>

Sven Neumann wrote:

> I don't have a strong opinion on that. The DBus control interface adds
> about 24kB to the the wpa_supplicant binary size. People might have DBus
> enabled for some other reason and don't need this feature in
> wpa_supplicant. But then, perhaps it's just not worth the extra
> option...
> 
> 
> Sven

Being the one "guilty" of wpa_supplicant updates i don't have a strong
opinion on this either.
On one side wpa_supplicant has it's own way of controlling itself via
wpa_cli and thus somewhat negates the need for dbus bindings.
On the other side you may not want to fork to call wpa_cli and/or learn
the wpa_supplicant/cli controlling protocol (or other good reasons), and
if you already have dbus enabled those extra 24k probably won't hurt
that much in the global scheme of things - after all people who want to
save that last KB will probably steer away from dbus.
Regards.

  reply	other threads:[~2009-07-13 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  8:20 [Buildroot] [PATCH] optional DBus support in wpa_supplicant Sven Neumann
2009-07-13  9:13 ` Sven Neumann
2009-07-13 10:44   ` Peter Korsgaard
2009-07-13 14:32     ` Sven Neumann
2009-07-13 15:05       ` Gustavo Zacarias [this message]
2009-07-13 18:26         ` Peter Korsgaard
2009-07-14 11:04           ` Sven Neumann
2009-07-14 19:20             ` Peter Korsgaard
2009-07-15  8:11               ` Sven Neumann
2009-07-20 11:39                 ` Sven Neumann
2009-07-20 20:13                   ` Peter Korsgaard

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=4A5B4D46.6010807@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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