From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 1/2] package/*: test for BR2_PACKAGE_LIBGUDEV for dependency
Date: Wed, 18 Nov 2015 21:55:20 +0100 [thread overview]
Message-ID: <20151118215520.76ee0f5e@free-electrons.com> (raw)
In-Reply-To: <fe0244022307f4d80793175f3d433c3e4ae9b738.1447875520.git.baruch@tkos.co.il>
Dear Baruch Siach,
On Wed, 18 Nov 2015 21:38:39 +0200, Baruch Siach wrote:
> Make the case of adding libgudev as a dependency more consistent with all
> other dependency packages. The <pkg>_DEPENDENCIES variable sets the build
> order which is conceptually independent of the underlying reason for that
> dependency.
>
> Also, remove the comments in hidapi.mk and udisks.mk. These comments explain
> why BR2_PACKAGE_LIBGUDEV is selected, so the comments in corresponding
> Config.in files are enough.
>
> Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/hidapi/hidapi.mk | 7 +------
> package/libmbim/libmbim.mk | 2 +-
> package/modem-manager/modem-manager.mk | 2 +-
> package/network-manager/network-manager.mk | 2 +-
> package/udisks/udisks.mk | 7 +------
> 5 files changed, 5 insertions(+), 15 deletions(-)
Both patches applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-11-18 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 19:38 [Buildroot] [PATCH next 1/2] package/*: test for BR2_PACKAGE_LIBGUDEV for dependency Baruch Siach
2015-11-18 19:38 ` [Buildroot] [PATCH next 2/2] udisks: make libgudev selection consistent Baruch Siach
2015-11-18 20:55 ` 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=20151118215520.76ee0f5e@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