From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com> To: Stanislaw Gruszka <sgruszka@redhat.com> Cc: Arnd Bergmann <arnd@arndb.de>, Kalle Valo <kvalo@codeaurora.org>, Felix Fietkau <nbd@nbd.name>, "David S. Miller" <davem@davemloft.net>, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mt76: fix building without CONFIG_MT76x0U Date: Wed, 26 Sep 2018 17:48:49 +0200 [thread overview] Message-ID: <20180926154848.GB3153@localhost.localdomain> (raw) In-Reply-To: <20180926140627.GA9265@redhat.com> > On Wed, Sep 26, 2018 at 02:51:59PM +0200, Arnd Bergmann wrote: > > The recent rework of the mt76 driver caused build failures in > > configurations that leave the mt76x0u support disabled: > > > > ERROR: "mt76u_mcu_deinit" [drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0-common.ko] undefined! > > ERROR: "mt76x02u_set_txinfo" [drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0-common.ko] undefined! > > ERROR: "mt76u_queues_deinit" [drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0-common.ko] undefined! > > ERROR: "mt76u_stop_stat_wk" [drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0-common.ko] undefined! > > > > I think there not yet posted Lorenzo patches that fix this build > problem. Hi Arnd, adding mt76x0e hw initialization I have already fixed mt76u_mcu_deinit, mt76u_queues_deinit and mt76u_stop_stat_wk (I have not posted the patchset yet, I will send it later today or tomorrow). mt76x02u_set_txinfo needs to be fixed since I have not worked on mt76x0e tx path yet, but it is on my ToDo list. Regards, Lorenzo > > Regards > Stanislaw >
WARNING: multiple messages have this Message-ID (diff)
From: Lorenzo Bianconi <lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> To: Stanislaw Gruszka <sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Cc: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>, Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>, Felix Fietkau <nbd-Vt+b4OUoWG0@public.gmane.org>, "David S. Miller" <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>, linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: [PATCH] mt76: fix building without CONFIG_MT76x0U Date: Wed, 26 Sep 2018 17:48:49 +0200 [thread overview] Message-ID: <20180926154848.GB3153@localhost.localdomain> (raw) In-Reply-To: <20180926140627.GA9265-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> > On Wed, Sep 26, 2018 at 02:51:59PM +0200, Arnd Bergmann wrote: > > The recent rework of the mt76 driver caused build failures in > > configurations that leave the mt76x0u support disabled: > > > > ERROR: "mt76u_mcu_deinit" [drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0-common.ko] undefined! > > ERROR: "mt76x02u_set_txinfo" [drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0-common.ko] undefined! > > ERROR: "mt76u_queues_deinit" [drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0-common.ko] undefined! > > ERROR: "mt76u_stop_stat_wk" [drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0-common.ko] undefined! > > > > I think there not yet posted Lorenzo patches that fix this build > problem. Hi Arnd, adding mt76x0e hw initialization I have already fixed mt76u_mcu_deinit, mt76u_queues_deinit and mt76u_stop_stat_wk (I have not posted the patchset yet, I will send it later today or tomorrow). mt76x02u_set_txinfo needs to be fixed since I have not worked on mt76x0e tx path yet, but it is on my ToDo list. Regards, Lorenzo > > Regards > Stanislaw >
next prev parent reply other threads:[~2018-09-26 15:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-09-26 12:51 [PATCH] mt76: fix building without CONFIG_MT76x0U Arnd Bergmann 2018-09-26 14:06 ` Stanislaw Gruszka 2018-09-26 15:43 ` Arnd Bergmann 2018-09-26 15:48 ` Lorenzo Bianconi [this message] 2018-09-26 15:48 ` Lorenzo Bianconi 2018-09-27 15:22 ` kbuild test robot
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=20180926154848.GB3153@localhost.localdomain \ --to=lorenzo.bianconi@redhat.com \ --cc=arnd@arndb.de \ --cc=davem@davemloft.net \ --cc=kvalo@codeaurora.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-wireless@vger.kernel.org \ --cc=nbd@nbd.name \ --cc=netdev@vger.kernel.org \ --cc=sgruszka@redhat.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: linkBe 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.