From: "Nitin Gupta" <nitingupta910@gmail.com>
To: "Bret Towe" <magnade@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"Richard Purdie" <richard@openedhand.com>,
linux-mm-cc@laptop.org, "Satyam Sharma" <satyam.sharma@gmail.com>
Subject: Re: [RFC] LZO de/compression support - take 3
Date: Fri, 25 May 2007 23:03:33 +0530 [thread overview]
Message-ID: <4cefeab80705251033g6c8bdfb0l1499befb355b9c0f@mail.gmail.com> (raw)
In-Reply-To: <dda83e780705251002hed0e861x26a0b0ea6260dd52@mail.gmail.com>
On 5/25/07, Bret Towe <magnade@gmail.com> wrote:
> On 5/24/07, Nitin Gupta <nitingupta910@gmail.com> wrote:
> > On 5/25/07, Bret Towe <magnade@gmail.com> wrote:
> > > On 5/24/07, Nitin Gupta <nitingupta910@gmail.com> wrote:
> > > > On 5/23/07, Bret Towe <magnade@gmail.com> wrote:
> > > > > On 5/23/07, Nitin Gupta <nitingupta910@gmail.com> wrote:
>
> [ 237.556167] LZO compress successful: orig_size=17448, comp_size=8183
> [ 253.320760] LZO decompress successful: decomp_size=17448
>
> 2221c586e3eb869af7f4333d4f56b441b9aa8414 test-input
> 2e6c96b687274b629308b29835cebd3af989e0c7 output
>
> ppc however seems bust
> the computer is a g4 mini
Since lzo1x_decompress() itself is saying that decompression was
successful, it is really strange to have different sha-sums. It seems
that it's the fault with compress-test module itself. I will look more
closely into this and reply back.
Thanks,
Nitin
next prev parent reply other threads:[~2007-05-25 17:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 8:27 Nitin Gupta
2007-05-23 10:53 ` Michael-Luke Jones
2007-05-23 11:39 ` Nitin Gupta
2007-05-23 13:57 ` Michael-Luke Jones
2007-05-23 14:03 ` Nitin Gupta
2007-05-23 14:10 ` Michael-Luke Jones
2007-05-23 14:21 ` Nitin Gupta
2007-05-23 14:33 ` Michael-Luke Jones
2007-05-24 22:41 ` Richard Purdie
2007-05-24 22:54 ` Andrew Morton
2007-05-24 23:00 ` Richard Purdie
2007-05-23 16:16 ` Andrew Morton
2007-05-23 16:49 ` Richard Purdie
2007-05-24 4:04 ` Nitin Gupta
2007-05-25 10:42 ` Pavel Machek
2007-05-26 10:23 ` Michael-Luke Jones
2007-05-26 11:17 ` Nitin Gupta
2007-05-23 14:50 ` Bret Towe
2007-05-24 13:48 ` Nitin Gupta
2007-05-25 2:38 ` Bret Towe
2007-05-25 5:10 ` Nitin Gupta
2007-05-25 17:02 ` Bret Towe
2007-05-25 17:33 ` Nitin Gupta [this message]
2007-05-26 11:30 ` Nitin Gupta
2007-05-27 3:39 ` Bret Towe
2007-05-23 19:34 ` Satyam Sharma
2007-05-24 4:37 ` Nitin Gupta
2007-05-24 10:49 ` Satyam Sharma
2007-05-24 8:25 ` Richard Purdie
2007-05-24 11:07 ` Satyam Sharma
2007-05-24 14:29 ` Nitin Gupta
2007-05-24 19:12 ` Satyam Sharma
2007-05-24 14:20 ` Nitin Gupta
2007-05-24 20:09 ` Satyam Sharma
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=4cefeab80705251033g6c8bdfb0l1499befb355b9c0f@mail.gmail.com \
--to=nitingupta910@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm-cc@laptop.org \
--cc=magnade@gmail.com \
--cc=richard@openedhand.com \
--cc=satyam.sharma@gmail.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
all inboxes | Powered by JetHome®