linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael-lists@free-electrons.com>
To: Alain Knaff <alain@knaff.lu>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-embedded mailing list <linux-embedded@vger.kernel.org>
Subject: Status of bzip2 and lzma kernel compression for ARM?
Date: Wed, 24 Jun 2009 22:22:23 +0200	[thread overview]
Message-ID: <4A428AFF.20307@free-electrons.com> (raw)

Hi Alain,

I would like to test bzip2 and lzma compression on ARM.

Would you mind telling me what the status of your patches on ARM is, now
that the x86  and architecture independent code has been merged? Have
you or has anyone already updated them for 2.6.30, or shall I update
them by myself?

Thank you in advance,

Cheers,

Michael.

-- 
Michael Opdenacker, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com


-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

             reply	other threads:[~2009-06-24 20:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 20:22 Michael Opdenacker [this message]
2009-06-25  8:56 ` Status of bzip2 and lzma kernel compression for ARM? Mike Rapoport
2009-06-25  9:04   ` Florian Fainelli
2009-06-25 15:24     ` Michael Opdenacker
2009-06-25 17:08       ` Paul Mundt
2009-06-28 13:57       ` Alain Knaff
2009-06-28 14:47         ` Alain Knaff
2009-06-29 12:21           ` Mike Rapoport
2009-06-29 16:39             ` Michael Opdenacker
2009-07-03 15:43             ` Albin Tonnerre
2009-07-13 19:17               ` Albin Tonnerre

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=4A428AFF.20307@free-electrons.com \
    --to=michael-lists@free-electrons.com \
    --cc=alain@knaff.lu \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).