From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Chan Jeong <chan.jeong@lge.com>
Cc: squashfs-devel@lists.sourceforge.net,
'Gunho Lee' <gunho.lee@lge.com>,
'Tim Bird' <tim.bird@am.sony.com>,
linux-embedded@vger.kernel.org, 'Hyo Jun Im' <hyojun.im@lge.com>
Subject: Re: [Squashfs-devel] [PATCH 1/2] Squashfs: add LZO decompression support
Date: Mon, 24 May 2010 03:49:05 +0100 [thread overview]
Message-ID: <4BF9E921.6090609@lougher.demon.co.uk> (raw)
In-Reply-To: <001a01caf63e$0280ef50$0782cdf0$@jeong@lge.com>
Chan Jeong wrote:
> Hi,
>
> This patch series adds LZO decompression support to Squashfs,
> using in-kernel LZO decompression library and Squashfs
> decompressor entries.
>
> The patch series also includes LZO support for Squashfs tools.
>
> Signed-off-by: Chan Jeong <chan.jeong@lge.com>
Hi Chan
Thanks for the patches. How much testing have these patches had?
From an eyeball of the code (and a check of the LZO decompressor
code in the kernel) they look OK.
I'm currently considering whether to push these for mainline in
the current 2.6.35 merge window. I'd like to push them in this
merge window, however, pushing them now is definitely cutting things
fine because they were only posted for review after the merge window
opened (and the established etiquette is the merge window is to push
things that were posted for review and ideally in linux-next well
before the merge window opened).
So, some idea of how much testing these patches have had would
increase my confidence about pushing them in this merge window.
Thanks
Phillip
next parent reply other threads:[~2010-05-24 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a01caf63e$0280ef50$0782cdf0$@jeong@lge.com>
2010-05-24 2:49 ` Phillip Lougher [this message]
[not found] ` <4BF9E921.6090609-cnXvMjJKhjYG2Il/BtU0GPXRex20P6io@public.gmane.org>
2010-05-24 6:53 ` [PATCH 1/2] Squashfs: add LZO decompression support Chan Jeong
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=4BF9E921.6090609@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=chan.jeong@lge.com \
--cc=gunho.lee@lge.com \
--cc=hyojun.im@lge.com \
--cc=linux-embedded@vger.kernel.org \
--cc=squashfs-devel@lists.sourceforge.net \
--cc=tim.bird@am.sony.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