linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kaloz@openwrt.org (Imre Kaloz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: support XZ compressed kernels
Date: Fri, 08 Jul 2011 23:21:19 +0200	[thread overview]
Message-ID: <op.vybj9tox2s3iss@ecaz> (raw)
In-Reply-To: <20110708210407.GY4812@n2100.arm.linux.org.uk>

On Fri, 08 Jul 2011 23:04:07 +0200, Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:

> On Fri, Jul 08, 2011 at 10:54:29PM +0200, Imre Kaloz wrote:
>> On Fri, 08 Jul 2011 22:38:32 +0200, Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
>>
>>> On Thu, Jul 07, 2011 at 12:19:59PM +0200, Imre Kaloz wrote:
>>>>  # Make sure files are removed during clean
>>>> -extra-y       += piggy.gzip piggy.lzo piggy.lzma lib1funcs.S
>>>> +extra-y       += piggy.gzip piggy.lzo piggy.lzma piggy.xzkern lib1funcs.S ashldi3.S
>>>
>>> Is there a reason the suffix is xzkern rather than just xz ?
>>
>> We do "$(call if_changed,$(suffix_y))" and scripts/Makefile.lib
>> uses cmd_xzkern. I think keeping the changes minimal worth more
>> then having the proper suffix for a temporary file.
>
> Hmm, that's unfortunate.  It seems that it may be a non-standard format
> so I guess that's reasonable.  No further comments then.
>

Indeed. After the .gitignore modification, should I resend it here or it can go into the patch system?


Imre

      reply	other threads:[~2011-07-08 21:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 10:19 [PATCH] ARM: support XZ compressed kernels Imre Kaloz
2011-07-07 19:14 ` Nicolas Pitre
2011-07-08 18:50   ` Imre Kaloz
2011-07-08 20:38 ` Russell King - ARM Linux
2011-07-08 20:54   ` Imre Kaloz
2011-07-08 21:04     ` Russell King - ARM Linux
2011-07-08 21:21       ` Imre Kaloz [this message]

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=op.vybj9tox2s3iss@ecaz \
    --to=kaloz@openwrt.org \
    --cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).