Re: linux-next: build failure after merge of the wireless-drivers-next tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Aug 03, 2018 at 11:11:40AM +0200, Stanislaw Gruszka wrote:
> Hi
> 
> On Fri, Aug 03, 2018 at 06:29:42PM +1000, Stephen Rothwell wrote:
> > After merging the wireless-drivers-next tree, today's linux-next build
> > (powerpc allyesconfig) failed like this:
> [snip]
> > diff --git a/drivers/net/wireless/mediatek/mt76/Kconfig b/drivers/net/wireless/mediatek/mt76/Kconfig
> > index 850611ad347a..ad56b3ed2be2 100644
> > --- a/drivers/net/wireless/mediatek/mt76/Kconfig
> > +++ b/drivers/net/wireless/mediatek/mt76/Kconfig
> > @@ -13,6 +13,7 @@ config MT76x0U
> >  	tristate "MediaTek MT76x0U (USB) support"
> >  	depends on MAC80211
> >  	depends on USB
> > +	depends on BROKEN
> Would be better to limit driver to be build as module.
> Hopefully that will fix the issue. I'll post patch in a moment.

Ok, I made config allyesconfig and .config file looks like this:

CONFIG_WLAN_VENDOR_MEDIATEK=y
CONFIG_MT7601U=y
CONFIG_MT76_CORE=y
CONFIG_MT76_USB=y
CONFIG_MT76x2_COMMON=y
CONFIG_MT76x0U=m

However I still not sure if kernel will build this way.
Because there can be conflict between kernel symbols
and module symbols. So looks as part of quick fix
mt7601u should be build also as module. And slower
fix will be to rename symbosl names in mt76x0 driver.

Regards
Stanislaw
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux