From: Randy Dunlap <randy.dunlap@oracle.com>
To: Richard Purdie <rpurdie@openedhand.com>
Cc: linux-crypto@vger.kernel.org,
linux-mtd <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
herbert@gondor.apana.org.au
Subject: Re: [PATCH 2/5] jffs2: Add LZO compression support to jffs2
Date: Tue, 1 May 2007 13:00:05 -0700 [thread overview]
Message-ID: <20070501130005.57ae0b49.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1178030823.5883.54.camel@localhost.localdomain>
On Tue, 01 May 2007 15:47:03 +0100 Richard Purdie wrote:
> Add LZO1X compression/decompression support to jffs2.
>
> LZO's interface doesn't entirely match that required by jffs2 so a
> buffer and memcpy is unavoidable.
>
> Signed-off-by: Richard Purdie <rpurdie@openedhand.com>
> ---
>
> diff --git a/fs/Kconfig b/fs/Kconfig
> index a42f767..1645dfa 100644
> --- a/fs/Kconfig
> +++ b/fs/Kconfig
> @@ -1310,6 +1310,16 @@ config JFFS2_ZLIB
>
> Say 'Y' if unsure.
>
> +config JFFS2_LZO
> + bool "JFFS2 LZO compression support" if JFFS2_COMPRESSION_OPTIONS
> + select LZO
> + depends on JFFS2_FS
> + default y
> + help
> + minilzo-based compression. Generally works better than Zlib.
> +
> + Say 'Y' if unsure.
Use <tab> on the "help" line (instead of spaces) and
use <tab><space><space> on the help text lines.
> config JFFS2_RTIME
> bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS
> depends on JFFS2_FS
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-05-01 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 14:47 [PATCH 2/5] jffs2: Add LZO compression support to jffs2 Richard Purdie
2007-05-01 20:00 ` Randy Dunlap [this message]
2007-05-04 9:06 ` Satyam Sharma
2007-05-04 10:52 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2007-05-04 11:45 Richard Purdie
2007-05-04 11:30 Richard Purdie
2007-05-04 11:35 ` David Woodhouse
2007-05-04 12:41 ` Haavard Skinnemoen
2007-05-04 12:47 ` David Woodhouse
2007-02-28 19:13 Richard Purdie
2007-04-25 12:35 ` David Woodhouse
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=20070501130005.57ae0b49.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dwmw2@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rpurdie@openedhand.com \
/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