Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V2 1/1] nvme: Allow libudev support
Date: Tue, 19 Apr 2016 10:01:50 +0200	[thread overview]
Message-ID: <20160419100150.158d763f@free-electrons.com> (raw)
In-Reply-To: <1461030864-11359-1-git-send-email-sam@mendozajonas.com>

Hello,

On Tue, 19 Apr 2016 11:54:24 +1000, Samuel Mendoza-Jonas wrote:
> Commands like 'nvme list' require libudev but support for libudev is
> decided at compile time, and in buildroot this is hard disabled.
> Add a check for udev and if it is available build nvme with udev
> support.
> 
> Signed-off-by: Samuel Mendoza-Jonas <sam@mendozajonas.com>

I've applied, after doing a few changes (since below).

> diff --git a/package/nvme/nvme.mk b/package/nvme/nvme.mk
> index 7c4bd8e..3571494 100755
> --- a/package/nvme/nvme.mk
> +++ b/package/nvme/nvme.mk
> @@ -8,11 +8,17 @@ NVME_VERSION = v0.3
>  NVME_SITE = $(call github,linux-nvme,nvme-cli,$(NVME_VERSION))
>  NVME_LICENSE = GPLv2+
>  NVME_LICENSE_FILES = LICENSE

I've added a comment here that insists on the fact that yes, LIBUDEV=0
enables udev support, while LIBUDEV=1 disables udev support, which is a
bit counter-intuitive.

> +ifeq ($(BR2_PACKAGE_HAS_UDEV),y)
> +NVME_DEPENDENCIES += udev
> +NVME_MAKE_OPTS = LIBUDEV=0

I've changed to use += here

> +else
> +NVME_MAKE_OPTS = LIBUDEV=1

and here, since it's a bit more future proof. It will avoid mistakes if
someone adds NVME_MAKE_OPTS = <something> outside of the conditional
block.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-04-19  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19  1:54 [Buildroot] [PATCH V2 1/1] nvme: Allow libudev support Samuel Mendoza-Jonas
2016-04-19  8:01 ` 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=20160419100150.158d763f@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