From: mwleeds@mailtundra.com
To: u-boot@lists.denx.de
Subject: [PATCH 0/5] zfs: Fix zfs support on aarch64
Date: Sat, 6 Apr 2024 18:47:24 -0700 [thread overview]
Message-ID: <20240407014743.13872-1-mwleeds@mailtundra.com> (raw)
This patch series is needed to get U-Boot to boot from a ZFS filesystem
on an aarch64 computer. Some of the patches are not architecture specific
and would be needed to boot ZFS on other platforms as well. The ZFS
support in U-Boot hasn't been substantively touched in several years and
to me it seems like it must have been broken for a long time on all
platforms, but I have only tested on aarch64.
Since there doesn't seem to be a mantainer for this area who I can cc,
I'm hoping these patches get seen and pulled in by a general U-Boot
maintainer.
Phaedrus Leeds (5):
zfs: Fix malloc() success check
zfs: Add a comment to clarify nvlist memory layout
zfs: Fix unaligned read of uint64
zfs: Fix return value of fs_devread()
zfs: Fix zfs_read() to actually work
fs/zfs/dev.c | 2 +-
fs/zfs/zfs.c | 30 ++++++++++++++++++++++++++----
2 files changed, 27 insertions(+), 5 deletions(-)
--
2.44.0
next reply other threads:[~2024-04-07 2:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 1:47 mwleeds [this message]
2024-04-07 1:47 ` [PATCH 1/5] zfs: Fix malloc() success check mwleeds
2024-04-07 11:22 ` Igor Opaniuk
2024-04-12 15:54 ` mwleeds
2024-04-07 1:47 ` [PATCH 2/5] zfs: Add a comment to clarify nvlist memory layout mwleeds
2024-04-07 1:47 ` [PATCH 3/5] zfs: Fix unaligned read of uint64 mwleeds
2024-04-12 18:50 ` Caleb Connolly
2024-04-12 18:57 ` Caleb Connolly
2024-04-25 4:02 ` mwleeds
2024-04-25 11:57 ` Caleb Connolly
2024-05-08 14:54 ` Phaedrus Leeds
2024-05-08 20:04 ` mwleeds
2024-04-07 1:47 ` [PATCH 4/5] zfs: Fix return value of fs_devread() mwleeds
2024-04-07 1:47 ` [PATCH 5/5] zfs: Fix zfs_read() to actually work mwleeds
2024-04-17 19:15 ` [PATCH 0/5] zfs: Fix zfs support on aarch64 Tom Rini
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=20240407014743.13872-1-mwleeds@mailtundra.com \
--to=mwleeds@mailtundra.com \
--cc=u-boot@lists.denx.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).