From: Guenter Roeck <linux@roeck-us.net>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: stable@vger.kernel.org
Subject: build errors in v3.18-stable-queue
Date: Tue, 25 Aug 2015 12:24:28 -0700 [thread overview]
Message-ID: <20150825192428.GA17707@roeck-us.net> (raw)
Build results:
total: 136 pass: 100 fail: 36
Failed builds:
alpha:allmodconfig
arm:allmodconfig
arm:imx_v6_v7_defconfig
arm:ixp4xx_defconfig
arm:multi_v5_defconfig
arm:rpc_defconfig
arm:axm55xx_defconfig
arm:vexpress_defconfig
arm:imx_v4_v5_defconfig
arm:shmobile_defconfig
arm:orion5x_defconfig
arm:cm_x2xx_defconfig
arm64:allmodconfig
avr32:defconfig
ia64:defconfig
mips:allmodconfig
mips:nlm_xlp_defconfig
mips:cavium_octeon_defconfig
parisc:allmodconfig
parisc:generic-32bit_defconfig
parisc:generic-64bit_defconfig
powerpc:defconfig
powerpc:allmodconfig
powerpc:ppc64e_defconfig
powerpc:cell_defconfig
powerpc:maple_defconfig
powerpc:ppc6xx_defconfig
powerpc:mpc83xx_defconfig
sparc32:allmodconfig
sparc64:allmodconfig
tile:tilegx_defconfig
unicore32:defconfig
x86_64:defconfig
x86_64:allyesconfig
x86_64:allmodconfig
xtensa:allmodconfig
Error log:
drivers/ata/libata-core.c:4243:32: error: 'ATA_HORKAGE_NOTRIM' undeclared here (not in a function)
make[2]: *** [drivers/ata/libata-core.o] Error 1
Guenter
next reply other threads:[~2015-08-25 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 19:24 Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-28 10:45 Build errors in v3.18-stable-queue Guenter Roeck
2016-03-01 0:24 ` Sasha Levin
2016-03-01 1:14 ` Gavin Shan
2016-03-01 2:47 ` Guenter Roeck
2016-03-01 5:06 ` Gavin Shan
2016-03-01 15:19 ` Sasha Levin
2016-03-01 23:17 ` Gavin Shan
2016-03-06 22:38 ` Gavin Shan
2016-03-02 4:31 ` Guenter Roeck
2016-03-01 11:12 ` Youngmin Nam
2016-03-01 15:18 ` Sasha Levin
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=20150825192428.GA17707@roeck-us.net \
--to=linux@roeck-us.net \
--cc=sasha.levin@oracle.com \
--cc=stable@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).