Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1699869
| From | Laurentiu Tudor <laurentiu.tudor@nxp.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) |
| Date | 2017-07-31 12:00 +0200 |
| Message-ID | <u9fEt-4EG-9@gated-at.bofh.it> (permalink) |
| References | <u9fl8-4xv-35@gated-at.bofh.it> <u9fl8-4xv-33@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
>
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Stephen Rothwell <sfr@canb.auug.org.au> - 2017-07-31 11:40 +0200
Re: linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Laurentiu Tudor <laurentiu.tudor@nxp.com> - 2017-07-31 12:00 +0200
Re: linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Greg KH <gregkh@linuxfoundation.org> - 2017-07-31 18:00 +0200
Re: linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Laurentiu Tudor <laurentiu.tudor@nxp.com> - 2017-08-01 10:30 +0200
Re: linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Stephen Rothwell <sfr@canb.auug.org.au> - 2017-08-07 02:30 +0200
Re: linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Stephen Rothwell <sfr@canb.auug.org.au> - 2017-08-11 01:50 +0200
Re: linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Greg KH <gregkh@linuxfoundation.org> - 2017-08-11 01:50 +0200
Re: linux-next: build failure in the staging tree (Was: kisskb: FAILED linux-next/s390-allmodconfig/s390x Mon Jul 31, 17:24) Stephen Rothwell <sfr@canb.auug.org.au> - 2017-08-11 02:10 +0200
csiph-web