From: Bjorn Helgaas <helgaas@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@vger.kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: Tree for Sep 6 (*msi.c but ! PCI_MSI)
Date: Wed, 6 Sep 2017 13:03:53 -0500 [thread overview]
Message-ID: <20170906180353.GA29570@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <ab28c8c3-94b9-5448-ca91-307c686a1903@infradead.org>
[+cc Marc, Thomas]
On Wed, Sep 06, 2017 at 08:53:04AM -0700, Randy Dunlap wrote:
> On 09/05/17 22:57, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do not add any v4.15 related material to your linux-next
> > included branches until after v4.14-rc1 has been released.
> >
> > Changes since 20170905:
> >
>
> on i386:
>
> CONFIG_PCI is not enabled, so CONFIG_PCI_MSI is not enabled.
>
>
> ../kernel/irq/msi.c: In function 'msi_domain_alloc_irqs':
> ../kernel/irq/msi.c:352:19: error: storage size of 'arg' isn't known
> msi_alloc_info_t arg;
> ^
>
> ../drivers/base/platform-msi.c:37:19: error: field 'arg' has incomplete type
> msi_alloc_info_t arg;
> ^
Thanks. I assume this is a new regression in next-20170906, since
you're responding to its announcement?
I don't quite see where the problem is yet (looking at next-20170906).
kernel/irq/msi.c includes linux/msi.h, which includes
arch/x86/include/asm/msi.h, which includes
arch/x86/include/asm/hw_irq.h and has a typedef for msi_alloc_info_t,
but I don't see any CONFIG_PCI guards there that would be relevant.
Bjorn
next prev parent reply other threads:[~2017-09-06 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 5:57 linux-next: Tree for Sep 6 Stephen Rothwell
2017-09-06 15:53 ` linux-next: Tree for Sep 6 (*msi.c but ! PCI_MSI) Randy Dunlap
2017-09-06 18:03 ` Bjorn Helgaas [this message]
2017-09-06 18:14 ` Randy Dunlap
2017-09-06 21:37 ` Bjorn Helgaas
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=20170906180353.GA29570@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.