From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] network-manager: follow udev changes
Date: Sat, 28 Apr 2012 17:30:03 +0200 [thread overview]
Message-ID: <201204281730.04194.arnout@mind.be> (raw)
In-Reply-To: <1334657953-29113-2-git-send-email-s.neumann@raumfeld.com>
On Tuesday 17 April 2012 12:19:13 Sven Neumann wrote:
> NetworkManager needs to select BR2_PACKAGE_UDEV_GUDEV.
>
> Signed-off-by: Sven Neumann <s.neumann@raumfeld.com>
I would include this one in the previous patch, otherwise the previous
patch breaks the build.
Regards,
Arnout
> ---
> package/network-manager/Config.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/network-manager/Config.in b/package/network-manager/Config.in
> index fb0c0e9..d14edd2 100644
> --- a/package/network-manager/Config.in
> +++ b/package/network-manager/Config.in
> @@ -7,7 +7,7 @@ config BR2_PACKAGE_NETWORK_MANAGER
> depends on BR2_USE_WCHAR # libglib2
> select BR2_PACKAGE_DBUS_GLIB
> select BR2_PACKAGE_UDEV
> - select BR2_PACKAGE_UDEV_ALL_EXTRAS
> + select BR2_PACKAGE_UDEV_GUDEV
> select BR2_PACKAGE_GNUTLS
> select BR2_PACKAGE_LIBNL
> select BR2_PACKAGE_UTIL_LINUX
>
--
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-04-28 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 10:19 [Buildroot] [PATCH 1/2] udev: replace UDEV_ALL_EXTRAS with more fine-grained options Sven Neumann
2012-04-17 10:19 ` [Buildroot] [PATCH 2/2] network-manager: follow udev changes Sven Neumann
2012-04-28 15:30 ` Arnout Vandecappelle [this message]
2012-04-28 15:26 ` [Buildroot] [PATCH 1/2] udev: replace UDEV_ALL_EXTRAS with more fine-grained options Arnout Vandecappelle
2013-03-24 11:41 ` 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=201204281730.04194.arnout@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