All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 10/13] package/libblockdev: add support for swap plugin
Date: Sat, 25 Jul 2020 10:42:30 +0200	[thread overview]
Message-ID: <20200725104230.5e80d391@windsurf.home> (raw)
In-Reply-To: <20200724232601.2441272-11-aduskett@gmail.com>

On Fri, 24 Jul 2020 16:25:58 -0700
aduskett at gmail.com wrote:

> From: Adam Duskett <Aduskett@gmail.com>
> 
> Signed-off-by: Adam Duskett <Aduskett@gmail.com>
> ---
>  package/libblockdev/Config.in      | 4 ++++
>  package/libblockdev/libblockdev.mk | 7 ++++++-
>  2 files changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/package/libblockdev/Config.in b/package/libblockdev/Config.in
> index 82e317b25f..9d5d4e6071 100644
> --- a/package/libblockdev/Config.in
> +++ b/package/libblockdev/Config.in
> @@ -57,6 +57,10 @@ config BR2_PACKAGE_LIBBLOCKDEV_PARTED
>  comment "part plugin needs a toolchain w/ locale"
>  	depends on !BR2_ENABLE_LOCALE
>  
> +config BR2_PACKAGE_LIBBLOCKDEV_SWAP
> +	bool "swap"
> +	select BR2_PACKAGE_UTIL_LINUX_LIBBLKID

I think we should also select BR2_PACKAGE_UTIL_LINUX here.

> +ifeq ($(BR2_PACKAGE_LIBBLOCKDEV_SWAP),y)
> +LIBBLOCKDEV_CONF_OPTS += --with-swap

No build-time dependency on util-linux ?

> +else
> +LIBBLOCKDEV_CONF_OPTS += --without-swap
> +endif
> +
>  $(eval $(autotools-package))

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-07-25  8:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 23:25 [Buildroot] [PATCH v2 00/13] package/udisks: bump version to 2.9.0 aduskett at gmail.com
2020-07-24 23:25 ` [Buildroot] [PATCH v2 01/13] package/gettext-gnu: add msgfmt wrapper aduskett at gmail.com
2020-07-24 23:25 ` [Buildroot] [PATCH v2 02/13] package/libblockdev: new package aduskett at gmail.com
2020-07-24 23:25 ` [Buildroot] [PATCH v2 03/13] package/libbytesize: " aduskett at gmail.com
2020-07-24 23:25 ` [Buildroot] [PATCH v2 04/13] package/libblockdev: add support for crypto plugin aduskett at gmail.com
2020-07-24 23:25 ` [Buildroot] [PATCH v2 05/13] package/libblockdev: add support for fs plugin aduskett at gmail.com
2020-07-24 23:25 ` [Buildroot] [PATCH v2 06/13] package/libblockdev: add support for loop plugin aduskett at gmail.com
2020-07-24 23:25 ` [Buildroot] [PATCH v2 07/13] package/libblockdev: add support for lvm plugin aduskett at gmail.com
2020-07-25  8:40   ` Thomas Petazzoni
2020-07-24 23:25 ` [Buildroot] [PATCH v2 08/13] package/libblockdev: add support for mdraid plugin aduskett at gmail.com
2020-07-24 23:25 ` [Buildroot] [PATCH v2 09/13] package/libblockdev: add support for part plugin aduskett at gmail.com
2020-07-24 23:25 ` [Buildroot] [PATCH v2 10/13] package/libblockdev: add support for swap plugin aduskett at gmail.com
2020-07-25  8:42   ` Thomas Petazzoni [this message]
2020-07-24 23:25 ` [Buildroot] [PATCH v2 11/13] package/udisks/Config.in: alphabatize package selection aduskett at gmail.com
2020-07-24 23:26 ` [Buildroot] [PATCH v2 12/13] package/udisks/udisks.mk: alphabatize dependencies aduskett at gmail.com
2020-07-24 23:26 ` [Buildroot] [PATCH v2 13/13] package/udisks: bump version to 2.9.0 aduskett at gmail.com

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=20200725104230.5e80d391@windsurf.home \
    --to=thomas.petazzoni@bootlin.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 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.