From: Artem Bityutskiy <dedekind1@gmail.com>
To: Hyunchul Lee <hyc.lee@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org, Hyunchul Lee <cheol.lee@lge.com>,
kernel-team@lge.com
Subject: Re: [PATCH 0/3] ubifs: add lz4hc compression
Date: Wed, 01 Mar 2017 12:35:38 +0200 [thread overview]
Message-ID: <1488364538.3583.6.camel@gmail.com> (raw)
In-Reply-To: <20170301011224.GC15972@Hyeoncheol-PC00>
On Wed, 2017-03-01 at 10:12 +0900, Hyunchul Lee wrote:
> yes, it is an in-memory inode. but i think that there can be problem
> of
> backward compatibility. for example, if ubifs_ino_node's compr_type
> is
> 4 in flash, the previous version of ubifs could misinterpret it as 0,
> because ubifs_inode's compr_type(2-bit) is assigned
> ubifs_ino_nodes' compr_type at ubifs_iget.
Good point. I guess changing the in-memory compr_type to something
wider right away would be a good idea, even if no new compressors are
added.
next prev parent reply other threads:[~2017-03-01 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 5:16 [PATCH 0/3] ubifs: add lz4hc compression Hyunchul Lee
2017-02-28 5:16 ` [PATCH 1/3] ubifs: add lz4hc compressor Hyunchul Lee
2017-02-28 5:16 ` [PATCH 2/3] ubifs: change type of ubifs_inode's compr_type to unsigend:16 Hyunchul Lee
2017-02-28 10:17 ` [PATCH 0/3] ubifs: add lz4hc compression Artem Bityutskiy
2017-03-01 1:12 ` Hyunchul Lee
2017-03-01 10:35 ` Artem Bityutskiy [this message]
2017-03-03 8:08 ` Richard Weinberger
2017-03-03 11:07 ` Hyunchul Lee
2017-03-03 12:00 ` Artem Bityutskiy
2017-03-03 12:07 ` Richard Weinberger
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=1488364538.3583.6.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=cheol.lee@lge.com \
--cc=hyc.lee@gmail.com \
--cc=kernel-team@lge.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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.