All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "José Luis Salvador Rufo" <salvador.joseluis@gmail.com>
Cc: Alexander Mukhin <alexander.i.mukhin@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/zfs: bump version to 2.2.4
Date: Mon, 22 Jul 2024 15:18:34 +0200	[thread overview]
Message-ID: <20240722151834.53981478@windsurf> (raw)
In-Reply-To: <CAH+XeQZrmvt7Ui7D6M2515=+W_3wTsPGVVWLcRALx+4X93Chzg@mail.gmail.com>

Hello José,

Thanks for your super quick feedback!

On Mon, 22 Jul 2024 15:01:45 +0200
José Luis Salvador Rufo <salvador.joseluis@gmail.com> wrote:

> In the meantime, I recommend the following options:
> 
> A) Revert to the previous version (OpenZFS v2.2.3). This is not ideal for
> people who have already upgraded.
> 
> B) Include a work-in-progress (it works for buildroot, I tested it) patch:
> https://github.com/openzfs/zfs/pull/16169.patch.

Please do this option (B), and also contribute SEEK_DATA support to
uClibc. I've added Waldemar, the uClibc-ng maintainer, in Cc.

Thanks a lot!

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:[~2024-07-22 13:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 18:18 [Buildroot] [PATCH 1/1] package/zfs: bump version to 2.2.4 Alexander Mukhin
2024-05-27  9:19 ` Peter Korsgaard
2024-06-08 15:28 ` Peter Korsgaard
2024-07-22 12:47 ` Thomas Petazzoni via buildroot
2024-07-22 13:01   ` José Luis Salvador Rufo
2024-07-22 13:18     ` Thomas Petazzoni via buildroot [this message]
2024-08-04 13:31       ` José Luis Salvador Rufo
2024-08-05  6:25         ` Waldemar Brodkorb

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=20240722151834.53981478@windsurf \
    --to=buildroot@buildroot.org \
    --cc=alexander.i.mukhin@gmail.com \
    --cc=salvador.joseluis@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.