From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: 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 10:22:54 +1100 [thread overview]
Message-ID: <20100113102254.332dbf33.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100112083013.1dad8a8d.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
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.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-12 23:23 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 [this message]
2010-01-13 0:26 ` Phillip Lougher
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=20100113102254.332dbf33.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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 \
/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