kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [arm-soc:testing/defconfig-warnings 14/14] arch/arm/boot/compressed/../../../../lib/decompress_u
Date: Mon, 15 Oct 2012 13:30:12 +0000	[thread overview]
Message-ID: <201210151330.12940.arnd@arndb.de> (raw)
In-Reply-To: <20121015021801.GB7203@localhost>

On Monday 15 October 2012, Fengguang Wu wrote:
> FYI, kernel build failed on
> 
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git testing/defconfig-warnings
> head:   b8848fafef862602bfad86686d6da00dce80b9c6
> commit: b8848fafef862602bfad86686d6da00dce80b9c6 [14/14] Merge branches 'warnings/broken', 'warnings/mtd', 'warnings/missing' and 'warnings/randconfig' into HEAD
> config: arm-imx_v6_v7_defconfig # make ARCH=arm imx_v6_v7_defconfig
> 
> All error/warnings:
> 
> In file included from arch/arm/boot/compressed/decompress.c:43:0:
> arch/arm/boot/compressed/../../../../lib/decompress_unlzo.c:34:39: fatal error: lzo/lzo1x_decompress_safe.c: No such file or directory
> compilation terminated.

Ok, the bug is only present in -next, so I must not apply the fix on mainline.
I believe my fix was included in -next as well, so it should all be good now.

	Arnd

  parent reply	other threads:[~2012-10-15 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15  2:18 [arm-soc:testing/defconfig-warnings 14/14] arch/x86/boot/compressed/../../../../lib/decompress_unlzo Fengguang Wu
2012-10-15  2:18 ` [arm-soc:testing/defconfig-warnings 14/14] arch/arm/boot/compressed/../../../../lib/decompress_unlzo Fengguang Wu
2012-10-15 13:30 ` Arnd Bergmann [this message]
2012-10-15 13:32 ` [arm-soc:testing/defconfig-warnings 14/14] arch/arm/boot/compressed/../../../../lib/decompress_u Arnd Bergmann

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=201210151330.12940.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=kernel-janitors@vger.kernel.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).