All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] squashfs: do not force gzip support if lz4/xz/zstd is selected
Date: Fri, 7 Dec 2018 20:24:32 +0100	[thread overview]
Message-ID: <20181207202432.76868c40@gmx.net> (raw)
In-Reply-To: <20181207131356.14366-1-peter@korsgaard.com>

Hello Peter,

On Fri,  7 Dec 2018 14:13:55 +0100, Peter Korsgaard <peter@korsgaard.com> wrote:

> The logic to ensure at least one compression backend is selected was not
> updated when lz4, xz and zstd were introduced -  Fix that.
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
>  package/squashfs/Config.in | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/package/squashfs/Config.in b/package/squashfs/Config.in
> index c16ebbf27f..fdd8833060 100644
> --- a/package/squashfs/Config.in
> +++ b/package/squashfs/Config.in
> @@ -2,7 +2,12 @@ config BR2_PACKAGE_SQUASHFS
>  	bool "squashfs"
>  	depends on BR2_TOOLCHAIN_HAS_THREADS
>  	depends on BR2_USE_MMU # fork()

Nitpick: maybe a short comment here is helpful (I missed the line while
adding zstd support)?

  # ensure at least on compression backend (defaults to gzip)

> -	select BR2_PACKAGE_SQUASHFS_GZIP if !(BR2_PACKAGE_SQUASHFS_LZMA || BR2_PACKAGE_SQUASHFS_LZO)
> +	select BR2_PACKAGE_SQUASHFS_GZIP if !( \
> +	       BR2_PACKAGE_SQUASHFS_LZ4 || \
> +	       BR2_PACKAGE_SQUASHFS_LZMA || \
> +	       BR2_PACKAGE_SQUASHFS_LZO || \
> +	       BR2_PACKAGE_SQUASHFS_XZ || \
> +	       BR2_PACKAGE_SQUASHFS_ZSTD)
>  	help
>  	  Tools to generate SquashFS filesystems.
>  

Reviewed-by: Peter Seiderer <ps.report@gmx.net>

Regards,
Peter

  reply	other threads:[~2018-12-07 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 13:13 [Buildroot] [PATCH] squashfs: do not force gzip support if lz4/xz/zstd is selected Peter Korsgaard
2018-12-07 19:24 ` Peter Seiderer [this message]
2018-12-07 23:12   ` Peter Korsgaard
2018-12-16 15:17 ` Peter Korsgaard

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=20181207202432.76868c40@gmx.net \
    --to=ps.report@gmx.net \
    --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.