From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>
Cc: "heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
"Linux-Next Mailing List" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 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 09:55:14 +0000 [thread overview]
Message-ID: <597EFE81.9010407@nxp.com> (raw)
In-Reply-To: <20170731193546.6d0538cf@canb.auug.org.au>
Hi Stephen,
That's because the fsl-mc driver selects GENERIC_MSI_IRQ_DOMAIN and not
all arches implement the support for the option. I can submit a patch
that adds explicit dependencies on arches that it was build-tested (x86,
arm, powerpc, all both 32 and 64 bits) similar to how it's done here
[1]. Let me know if you're ok with this fix and i'll submit the fix to
staging.
---
Thanks & Best Regards, Laurentiu
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/Kconfig#n28
On 07/31/2017 12:35 PM, Stephen Rothwell wrote:
> 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
>>
>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkisskb.ellerman.id.au%2Fkisskb%2Fbuildresult%2F13110910%2F&data=01%7C01%7Claurentiu.tudor%40nxp.com%7C0b58775ead154830f76f08d4d7f78d99%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0&sdata=A84bbMQe7VRz9OPK13PzaidBEfjm43Ik%2FbfCDJ89ZzM%3D&reserved=0
>>
>> 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.
>
next prev parent reply other threads:[~2017-07-31 9:55 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 ` linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Stephen Rothwell
2017-07-31 9:55 ` Laurentiu Tudor [this message]
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=597EFE81.9010407@nxp.com \
--to=laurentiu.tudor@nxp.com \
--cc=greg@kroah.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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