From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>
Cc: heiko.carstens@de•ibm.com,
Laurentiu Tudor <laurentiu.tudor@nxp•com>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
LKML <linux-kernel@vger•kernel.org>
Subject: linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24)
Date: Mon, 31 Jul 2017 19:35:46 +1000 [thread overview]
Message-ID: <20170731193546.6d0538cf@canb.auug.org.au> (raw)
In-Reply-To: <20170731072425.1.95853@222023911cb9>
Hi all,
On Mon, 31 Jul 2017 07:24:25 -0000 noreply@ellerman•id.au wrote:
>
> FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/13110910/
>
> Commit: Add linux-next specific files for 20170731
> 742f220ee69c8102eabea45e45d92aa18721fab1
> Compiler: s390x-linux-gcc (GCC) 4.6.3
>
> Possible errors
> ---------------
>
> include/linux/msi.h:196:21: fatal error: asm/msi.h: No such file or directory
> make[2]: *** [arch/s390/kernel/asm-offsets.s] Error 1
> make[1]: *** [prepare0] Error 2
> make: *** [sub-make] Error 2
Caused by commit
03274850279c ("staging: fsl-mc: allow the driver compile multi-arch")
I will revert that commit tomorrow unless it if fixed in the mean time.
--
Cheers,
Stephen Rothwell
next parent reply other threads:[~2017-07-31 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170731072425.1.95853@222023911cb9>
2017-07-31 9:35 ` Stephen Rothwell [this message]
2017-07-31 9:55 ` linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Laurentiu Tudor
2017-07-31 15:58 ` Greg KH
2017-08-01 8:29 ` Laurentiu Tudor
2017-08-07 0:22 ` Stephen Rothwell
2017-08-10 23:41 ` Stephen Rothwell
2017-08-10 23:48 ` Greg KH
2017-08-11 0:04 ` Stephen Rothwell
2017-08-14 22:19 ` Greg KH
2017-08-14 23:06 ` Stephen Rothwell
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=20170731193546.6d0538cf@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=greg@kroah$(echo .)com \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=laurentiu.tudor@nxp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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