From: Greg KH <gregkh@linuxfoundation.org>
To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"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 08:58:50 -0700 [thread overview]
Message-ID: <20170731155850.GD1262@kroah.com> (raw)
In-Reply-To: <597EFE81.9010407@nxp.com>
On Mon, Jul 31, 2017 at 09:55:14AM +0000, Laurentiu Tudor wrote:
> 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.
Ugh, you should not be selecting that option, but rather depending on
the option, right?
thanks,
greg k-h
next prev parent reply other threads:[~2017-07-31 15:58 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
2017-07-31 15:58 ` Greg KH [this message]
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=20170731155850.GD1262@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=laurentiu.tudor@nxp.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