All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jorgen Lundman <lundman@lundman.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [GIT PULL] ZFS: lundman/master
Date: Thu, 11 Jan 2018 09:12:04 +0900	[thread overview]
Message-ID: <5aadc44f-b5cd-5db2-e4e3-8b33601f60d7@lundman.net> (raw)
In-Reply-To: <20180110132843.GE2621@bill-the-cat>

> 
> I'm reluctant to just take this as-is.  That's a lot of code changes in
> a single commit that was not posted (as far as I can see) to the mailing
> list.  Can you break that down into a series of changes that can be
> reviewed and post that?  Thanks!
> 

I received an email that ZFS U-boot booting was tricky to get to work,
since it required old pool version, and didn't work at all with big endian.

When I first did ZFS, I took the GRUB sources in 2012. So this time around,
I collected the commits from 2012 to now, and merged them into u-boot. Some
~50 commits or so. It makes U-boot work with modern pools, and current
default compression (lz4) as well as raidz/mirror boots.

It is a large change, I agree. But I'm unsure how to split it into smaller
commits. It is mostly bring it up to current with its upstream.

If it is preferred to post to the ML, I will do so - I thought "git pull"
was an alternate. Please advice,

Lund

-- 
Jorgen Lundman       | <lundman@lundman.net>
Unix Administrator   | +81 (0)90-5578-8500
Shibuya-ku, Tokyo    | Japan

  reply	other threads:[~2018-01-11  0:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 13:04 [U-Boot] [GIT PULL] u-boot-uniphier/master Masahiro Yamada
2018-01-09 17:30 ` Tom Rini
2018-01-10  3:21 ` [U-Boot] [GIT PULL] ZFS: lundman/master Jorgen Lundman
2018-01-10 13:28   ` Tom Rini
2018-01-11  0:12     ` Jorgen Lundman [this message]
2018-01-11 16:29       ` 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=5aadc44f-b5cd-5db2-e4e3-8b33601f60d7@lundman.net \
    --to=lundman@lundman.net \
    --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 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.