public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Laurentiu Tudor <laurentiu.tudor@nxp.com>,
	"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: Thu, 10 Aug 2017 16:48:42 -0700	[thread overview]
Message-ID: <20170810234842.GA19410@kroah.com> (raw)
In-Reply-To: <20170811094109.2d314b7f@canb.auug.org.au>

On Fri, Aug 11, 2017 at 09:41:09AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Mon, 7 Aug 2017 10:22:08 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Tue, 1 Aug 2017 08:29:31 +0000 Laurentiu Tudor <laurentiu.tudor@nxp.com> wrote:
> > >
> > > On 07/31/2017 06:58 PM, Greg KH wrote:  
> > > > On Mon, Jul 31, 2017 at 09:55:14AM +0000, Laurentiu Tudor wrote:    
> > > >>
> > > >> 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?    
> > > 
> > > All users in the kernel use "select", so i don't think so. An 
> > > interesting use that adds explicit dependencies on architectures can be
> > > seen here [1], in the generic code. I've proposed a patch [2] that does 
> > > a similar thing for mc-bus. I think it's a good approach as it keeps 
> > > things under control by explicitly specifying the architectures on which
> > > the driver was compile-tested.
> > > 
> > > ---
> > > Best Regards, Laurentiu
> > > 
> > > [1] 
> > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/Kconfig#n28
> > > [2] https://patchwork.kernel.org/patch/9871861/  
> > 
> > Any resolution of this?
> 
> Ping?

I have a patch in my queue, somewhere, that should resolve this, I
think.  I have 600+ staging patches in my todo queue right now, that's
what I get for trying to have a vacation...

I'll get to it soon, it's not lost, thanks.

greg k-h

  reply	other threads:[~2017-08-10 23:48 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
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 [this message]
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=20170810234842.GA19410@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