From: Richard Purdie <richard@openedhand.com>
To: David Woodhouse <dwmw2@infradead.org>, herbert@gondor.apana.org.au
Cc: akpm <akpm@linux-foundation.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Kernel LZO compression + jffs2 and crypto usage
Date: Fri, 30 Mar 2007 11:11:58 +0100 [thread overview]
Message-ID: <1175249518.5822.18.camel@localhost.localdomain> (raw)
I've put the LZO patch series I sent a few weeks ago in a git tree:
http://git.o-hand.com/?p=linux-rpurdie;a=shortlog;h=linux-rpurdie-lzo
(git://git.o-hand.com/linux-rpurdie linux-rpurdie-lzo)
I'm not sure of the best way to merge this since it touches two
subsystems. David, do you want to pull the initial patch and jffs2 parts
and then the crpyto patch can follow through the crypto tree? I'm hoping
this can make 2.6.22.
Let me know if there is anything further I can do to help.
Cheers,
Richard
next reply other threads:[~2007-03-30 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 10:11 Richard Purdie [this message]
2007-03-30 11:18 ` Kernel LZO compression + jffs2 and crypto usage Herbert Xu
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=1175249518.5822.18.camel@localhost.localdomain \
--to=richard@openedhand.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.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