From: Matthias Kaehlcke <mka@chromium.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] zlib: Mark get_unaligned16() as __maybe_unused
Date: Mon, 22 May 2017 11:27:38 -0700 [thread overview]
Message-ID: <20170522182738.GK141096@google.com> (raw)
In-Reply-To: <201705221620.XOEATD0u%fengguang.wu@intel.com>
El Mon, May 22, 2017 at 04:57:30PM +0800 kbuild test robot ha dit:
> Hi Matthias,
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.12-rc2 next-20170522]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Matthias-Kaehlcke/zlib-Mark-get_unaligned16-as-__maybe_unused/20170522-112401
> config: powerpc-maple_defconfig (attached as .config)
> compiler: powerpc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=powerpc
>
> All errors (new ones prefixed by >>):
>
> >> arch/powerpc/boot/inffast.c:6:22: fatal error: compiler.h: No such file or directory
> #include "compiler.h"
> ^
> compilation terminated.
I was convinced I build tested this, but I can reproduce the error. I
guess we have to use the bare __attribute__((unused)) :/
prev parent reply other threads:[~2017-05-22 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 18:10 [PATCH v2] zlib: Mark get_unaligned16() as __maybe_unused Matthias Kaehlcke
2017-05-22 8:57 ` kbuild test robot
2017-05-22 18:27 ` Matthias Kaehlcke [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=20170522182738.GK141096@google.com \
--to=mka@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.