From: Kalle Valo <kvalo@codeaurora.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
"Matt Redfearn" <matt.redfearn@imgtec.com>,
"James Hogan" <jhogan@kernel.org>,
"Linux MIPS Mailing List" <linux-mips@linux-mips.org>,
matt.redfearn@mips.com
Subject: Re: [PATCH] bcma: Fix 'allmodconfig' and BCMA builds on MIPS targets
Date: Mon, 15 Jan 2018 12:11:33 +0200 [thread overview]
Message-ID: <87vag31ley.fsf@purkki.adurom.net> (raw)
In-Reply-To: <db5915ed-fc50-292f-c86b-4da7f3f0eddd@roeck-us.net> (Guenter Roeck's message of "Sun, 14 Jan 2018 13:40:50 -0800")
Guenter Roeck <linux@roeck-us.net> writes:
> [ copying linux-mips ]
>
> On 01/14/2018 01:34 PM, Guenter Roeck wrote:
>> Mips builds with BCMA host mode enabled fail in mainline and -next
>> with:
>>
>> In file included from include/linux/bcma/bcma.h:10:0,
>> from drivers/bcma/bcma_private.h:9,
>> from drivers/bcma/main.c:8:
>> include/linux/bcma/bcma_driver_pci.h:218:24: error:
>> field 'pci_controller' has incomplete type
>>
>> Bisect points to commit d41e6858ba58c ("MIPS: Kconfig: Set default MIPS
>> system type as generic") as the culprit. Analysis shows that the commmit
>> changes PCI configuration and enables PCI_DRIVERS_GENERIC. This in turn
>> disables PCI_DRIVERS_LEGACY. 'struct pci_controller' is, however, only
>> defined if PCI_DRIVERS_LEGACY is enabled.
>>
>> Ultimately that means that BCMA_DRIVER_PCI_HOSTMODE depends on
>> PCI_DRIVERS_LEGACY. Add the missing dependency.
>>
>> Fixes: d41e6858ba58c ("MIPS: Kconfig: Set default MIPS system type as ...")
>> Cc: Matt Redfearn <matt.redfearn@imgtec.com>
>> Cc: James Hogan <jhogan@kernel.org>
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>> ---
>> I am aware that this problem has been reported several times. I have
>> not been able to find a fix, but I may have missed it. If so, my
>> apologies for the noise.
>>
> I should have said "I have not been able to find a patch fixing it".
>
>> Also note that this is not the only fix required; commit d41e6858ba58c,
>> as simple as it looks like, does a pretty good job messing up
>> "mips:allmodconfig" builds.
>>
> ... nor did I find patch(es) fixing the other build problem(s) introduced
> by d41e6858ba58c.
As I forgot to cc linux-mips on my previous email: I'm planning to queue
this for v4.15.
Over the weeked I got this bcma patch, but don't know if it's related or
not:
bcma: Prevent build of PCI host features in module
https://patchwork.kernel.org/patch/10161087/
And Guenter's patch is:
https://patchwork.kernel.org/patch/10162839/
Which one should I take? Adding also Matt.
And Matt also submitted similar patch for ssb:
ssb: Prevent build of PCI host features in module
https://patchwork.kernel.org/patch/10161131/
--
Kalle Valo
next prev parent reply other threads:[~2018-01-15 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 21:34 [PATCH] bcma: Fix 'allmodconfig' and BCMA builds on MIPS targets Guenter Roeck
2018-01-14 21:40 ` Guenter Roeck
2018-01-15 10:11 ` Kalle Valo [this message]
2018-01-15 10:03 ` Kalle Valo
2018-01-15 10:23 ` James Hogan
2018-01-15 17:10 ` Paul Burton
2018-01-15 20:05 ` Guenter Roeck
2018-01-15 20:30 ` James Hogan
2018-01-15 20:58 ` Guenter Roeck
2018-01-16 19:15 ` Kalle Valo
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=87vag31ley.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matt.redfearn@imgtec.com \
--cc=matt.redfearn@mips.com \
--cc=zajec5@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).