From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: havasi@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd/include/linux jffs2.h,1.35,1.36
Date: Tue, 26 Jul 2005 16:08:47 +0200 [thread overview]
Message-ID: <20050726140847.GD30656@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <E1DxPLP-0004rN-Ld@phoenix.infradead.org>
On Tue, 26 July 2005 14:19:39 +0100, havasi@infradead.org wrote:
>
> Update of /home/cvs/mtd/include/linux
> In directory phoenix.infradead.org:/tmp/cvs-serv18673
>
> Modified Files:
> jffs2.h
> Log Message:
> [jffs2] removing compressor lzo and lzari
>
> Index: jffs2.h
> ===================================================================
> RCS file: /home/cvs/mtd/include/linux/jffs2.h,v
> retrieving revision 1.35
> retrieving revision 1.36
> diff -u -r1.35 -r1.36
> --- jffs2.h 24 Jul 2005 15:15:51 -0000 1.35
> +++ jffs2.h 26 Jul 2005 13:19:36 -0000 1.36
> @@ -43,8 +43,6 @@
> #define JFFS2_COMPR_COPY 0x04
> #define JFFS2_COMPR_DYNRUBIN 0x05
> #define JFFS2_COMPR_ZLIB 0x06
> -#define JFFS2_COMPR_LZO 0x07
> -#define JFFS2_COMPR_LZARI 0x08
> /* Compatibility flags. */
> #define JFFS2_COMPAT_MASK 0xc000 /* What do to if an unknown nodetype is found */
> #define JFFS2_NODE_ACCURATE 0x2000
This patch could cause problems. We have to make sure 0x07 and 0x08
are never handed out for new compressors, one way or another.
Ferenc, can you add a comment that those numbers are reserved or
obsoleted?
Jörn
--
Optimizations always bust things, because all optimizations are, in
the long haul, a form of cheating, and cheaters eventually get caught.
-- Larry Wall
next parent reply other threads:[~2005-07-26 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1DxPLP-0004rN-Ld@phoenix.infradead.org>
2005-07-26 14:08 ` Jörn Engel [this message]
2005-07-26 14:21 ` mtd/include/linux jffs2.h,1.35,1.36 Ferenc Havasi
2005-07-26 17:28 ` Jörn Engel
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=20050726140847.GD30656@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=havasi@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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