From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] package/wpa_supplicant: Fix systemd service for new DBus bus name
Date: Wed, 13 Apr 2016 22:02:53 +0200 [thread overview]
Message-ID: <20160413220253.1e34b413@free-electrons.com> (raw)
In-Reply-To: <1460556558-20307-1-git-send-email-m.niestroj@grinn-global.com>
Hello,
On Wed, 13 Apr 2016 16:09:18 +0200, Marcin Niestroj wrote:
> systemd service files were supplied with old DBus bus name. After
> service activation systemd was waiting for appearance of specified bus
> name to consider it started successfully. However, if wpa_supplicant was
> compiled only with new dbus interface name, then systemd didn't notice
> configured (old) DBus bus name appearance. In the end service was
> considered malfunctioning and it was deactivated.
>
> Add upstreamable patch [1], which updates systemd service BusName
> property according to configured DBus interface version.
>
> [1] http://lists.infradead.org/pipermail/hostap/2016-April/035599.html
>
> Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> Changes v3 -> v4:
> * Fix commit description (upstream -> upstreamable)
> (suggested by Arnout)
> * Add patch reference in hostap mailing list archive
> (suggested by Arnout)
Applied to master, thanks. Please submit your patch upstream to the
wpa_supplicant developers. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-04-13 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 14:09 [Buildroot] [PATCH v4] package/wpa_supplicant: Fix systemd service for new DBus bus name Marcin Niestroj
2016-04-13 20:02 ` Thomas Petazzoni [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=20160413220253.1e34b413@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