All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] allow wpa_supplicant to run on the dbus using the 'new' api
Date: Tue, 18 Dec 2012 18:06:10 +0100	[thread overview]
Message-ID: <50D0A282.8090405@mind.be> (raw)
In-Reply-To: <50D08DED.6070109@bears.org>

On 18/12/12 16:38, Gary Coulbourne wrote:
> Arnout Vandecappelle wrote:
>> Reviewing patches is more convenient for us if you do the following:
>>
>> * Send the patch in-line, preferably with git send-email, so we can
>> give comments in-line.
> Sorry. I'll keep that in mind next time. I'm a long time hacker, but not
> a long-time contributor to open source. :)
> Thanks for being gentle with the criticism; I am still feeling my way
> around what is proper etiquette.

  The gentle criticism is of course aimed at attracting more 
contributors... Did it work? :-)


>> * Keep the original author information - in this case, preferably by
>> keeping the original git authorship.
> I was only able to find a partial copy of it via a google search, so I
> didn't have the original.

  To find buildroot patches, patchwork is a good reference:
http://patchwork.ozlabs.org/project/buildroot/list/

> I didn't think about it at the time, but I
> should have gone and looked in the mailing list archives.
>> I did a quick comparison with Sven's patch and I don't see why you
>> removed the BR2_PACKAGE_WPA_SUPPLICANT_DBUS_OLD option.
> Purely ignorance on my part -- I didn't realize that it was a both/and
> rather than an either/or for that option.
>
> The reason I needed the fix is because connman is expecting the new API,
> and so fails to find wireless devices without wpa_supplicant using it.

  I resent the original patches (I forgot to put you in CC, sorry). Can 
you check if they work as is, and correct them if needed?


> The dbus fix I sent seperately makes dbus properly handle activation, so
> that it can start the wpa_supplicant. The test in the autoconf fails and
> says the fixes need to be done manually. (I suspect it is because dbus is
> cross compiled, so the tests can't run on the host)

  I'll have a look at it next and give some more gentle criticism :-)


  Regards,
  Arnout

-- 
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

      reply	other threads:[~2012-12-18 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 20:54 [Buildroot] [PATCH] allow wpa_supplicant to run on the dbus using the 'new' api Gary Coulbourne
2012-12-18  6:58 ` Arnout Vandecappelle
2012-12-18  7:52   ` [Buildroot] [PATCH RESEND 1/2] wpa-supplicant: add options to enable the new DBus interface Arnout Vandecappelle
2012-12-18  7:52     ` [Buildroot] [PATCH RESEND 2/2] wpa_supplicant: rework .config file editing Arnout Vandecappelle
2013-01-14 19:48     ` [Buildroot] [PATCH RESEND 1/2] wpa-supplicant: add options to enable the new DBus interface Peter Korsgaard
2012-12-18 15:38   ` [Buildroot] [PATCH] allow wpa_supplicant to run on the dbus using the 'new' api Gary Coulbourne
2012-12-18 17:06     ` Arnout Vandecappelle [this message]

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=50D0A282.8090405@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.