From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ext4 support is now merged
Date: Thu, 20 Sep 2012 11:40:41 -0700 [thread overview]
Message-ID: <20120920184041.GD1763@bill-the-cat> (raw)
Hey all,
I've merged the ext4 branch (and Stephen's cache-align fix) into master
and pushed. The only problem report we have currently is that for
sufficiently large partitions we _may_ have unreadable directories. I'm
committed to working through this issue and seeing what's going on, the
main problem right now being that my large ext4 USB disk is fine and
Rob's large ext4 disk (or image?) is not. ext[23] seems to be
uneffected (I know the Angstrom folks have been using an older version
of these patches for some time) so I believe the best course of action
right now is to push this out to a wider audience.
Thanks all!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120920/4501c913/attachment.pgp>
reply other threads:[~2012-09-20 18:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120920184041.GD1763@bill-the-cat \
--to=trini@ti.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