From: Sascha Hauer <s.hauer@pengutronix.de>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH v2] fs: jffs2: add initial support for reading jffs2
Date: Mon, 10 Feb 2020 09:40:23 +0100 [thread overview]
Message-ID: <20200210084023.fqwqzwge5nceaq6v@pengutronix.de> (raw)
In-Reply-To: <20200205091201.15248-1-s.trumtrar@pengutronix.de>
On Wed, Feb 05, 2020 at 10:12:01AM +0100, Steffen Trumtrar wrote:
> Import the jffs2 filesystem code from Linux v5.5-rc1 and convert it
> to work with barebox.
>
> Writing is *not* supported.
>
> Testing was done with a n25q256a-compatible QuadSPI chip on a
> SoCFPGA-based Socrates board.
>
> Testing was done with a combination of:
> user@somelinuxhost: mkfs.jffs2 --eraseblock=4 -d fs/jffs2/ -o jffs2.img
> root@target:~ flash_erase -j /dev/mtd5 0 0
> root@target:~ dd if=jffs2.img of=/dev/mtd5
> barebox@EBV SOCrates:/ mount /dev/mtd0.data
> (...)
> mounted /dev/mtd0.data on /mnt/mtd0.data
>
> Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> ---
>
> Notes:
> Changes in v2:
> - add some missing pr_fmt
> - fix multiple mount/umount cycles by moving compressor_init and
> create_slab_caches to jffs2_probe instead of init_jffs2_fs.
> jffs2_remove calls compressor_exit and destroy_slab_caches which
> in turn is called by umount. This lead to being unable to umount
> twice.
> - fix memory leaks
> - fix jffs2_get_block function
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2020-02-10 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 9:12 Steffen Trumtrar
2020-02-10 8:40 ` Sascha Hauer [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=20200210084023.fqwqzwge5nceaq6v@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.trumtrar@pengutronix.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