Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "José Luis Salvador Rufo" <salvador.joseluis@gmail.com>
Cc: Romain Naour <romain.naour@gmail.com>,
	Philippe Serbruyns <Philippe.Serbruyns@ugent.be>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/zfs: bump version to 2.0.6
Date: Sun, 14 Nov 2021 16:23:42 +0100	[thread overview]
Message-ID: <20211114162342.41447d34@windsurf> (raw)
In-Reply-To: <20211025123117.3605744-1-salvador.joseluis@gmail.com>

Hello José,

On Mon, 25 Oct 2021 14:31:18 +0200
José Luis Salvador Rufo <salvador.joseluis@gmail.com> wrote:

> Added patch from upstream that fixes the `make` executed from the
> `kernel.m4` in cross-platform-compilations environments.

There is no patch added in this proposed patch. It seems like this
commit log was not properly updated now that you're bumping to a new
version of ZFS.

> As this version brings support for kernel up to 5.14, we update the
> test cases to use the 5.14 kernel.
> 
> Signed-off-by: José Luis Salvador Rufo <salvador.joseluis@gmail.com>
> ---
> I didn't find another alternative yet to:
> ```
> ZFS_MAKE_ENV = $(LINUX_MAKE_FLAGS)
> ZFS_CONF_ENV = $(LINUX_MAKE_FLAGS)
> ```
> Any suggestion?

Did you try the suggestion from Arnout, which he made on August 28? See
https://lore.kernel.org/buildroot/1433accf-3050-0f2e-9701-3da87c8c7c12@mind.be/


> -class TestZfsGlibc(infra.basetest.BRTest):
> -    config = \
> -        """
> +class TestZfsBase(infra.basetest.BRTest):
> +    config = """

It seems like you are also refactoring the ZFS test cases to avoid
duplicating the configuration for the glibc and uclibc cases. This is a
good idea, but it should be done in a separate patch, before the ZFS
bump.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2021-11-14 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22 20:05 [Buildroot] [PATCH] package/zfs: Fix cross-platform-compilations José Luis Salvador Rufo
2021-08-22 20:27 ` Romain Naour
2021-08-22 20:38   ` José Luis Salvador Rufo
2021-08-22 20:52     ` Romain Naour
2021-08-22 21:27       ` José Luis Salvador Rufo
2021-08-22 21:43         ` Romain Naour
2021-08-22 22:54           ` José Luis Salvador Rufo
2021-08-24 21:53 ` Thomas Petazzoni
2021-09-21  7:58   ` José Luis Salvador Rufo
2021-10-25 12:31     ` [Buildroot] [PATCH] package/zfs: bump version to 2.0.6 José Luis Salvador Rufo
2021-11-14 15:23       ` 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=20211114162342.41447d34@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=Philippe.Serbruyns@ugent.be \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=salvador.joseluis@gmail.com \
    --cc=yann.morin.1998@free.fr \
    /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