public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip.lougher@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	albin.tonnerre@free-electrons.com, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Phillip Lougher <phillip@lougher.demon.co.uk>
Subject: Re: linux-next: Tree for January 12 (unlzo)
Date: Wed, 13 Jan 2010 00:26:56 +0000	[thread overview]
Message-ID: <bffbecbb1001121626j61fab30aj87048a17a2b091ff@mail.gmail.com> (raw)
In-Reply-To: <20100113102254.332dbf33.sfr@canb.auug.org.au>

On Tue, Jan 12, 2010 at 11:22 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Randy,
>
> On Tue, 12 Jan 2010 08:30:13 -0800 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>>
>> arch/x86/boot/compressed/../../../../lib/decompress_unlzo.c:53: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'parse_header'
>> arch/x86/boot/compressed/../../../../lib/decompress_unlzo.c:90: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'unlzo'
>>
>> Problem is the "INIT" there, seems to be undefined.
>
> Caused by an interaction between Linus' tree and the squashfs tree that
> is being worked on.  It should not occur with today's linux-next as the
> squashfs changes have been removed pending a fix.

This problem is caused by the introduction of the unlzo code in Linus'
tree, and some patches in
the squashfs-next tree that move things out of
include/linux/decompress/mm.h into separate
xxx_mm.h files for each decompressor.  These parches were, obviously,
done before the unlzo
code was present.

I've fixed the patches in the squashfs-next tree for unlzo, and the
breakage should be fixed :-)

Thanks

Phillip

  reply	other threads:[~2010-01-13  0:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12  6:17 linux-next: Tree for January 12 Stephen Rothwell
2010-01-12 16:22 ` linux-next: Tree for January 12 (input) Randy Dunlap
2010-01-12 16:24 ` linux-next: Tree for January 12 (backlight warning) Randy Dunlap
2010-01-12 16:30 ` linux-next: Tree for January 12 (unlzo) Randy Dunlap
2010-01-12 23:22   ` Stephen Rothwell
2010-01-13  0:26     ` Phillip Lougher [this message]
2010-01-19 16:38       ` Randy Dunlap

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=bffbecbb1001121626j61fab30aj87048a17a2b091ff@mail.gmail.com \
    --to=phillip.lougher@gmail.com \
    --cc=albin.tonnerre@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=phillip@lougher.demon.co.uk \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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