From: Kalle Valo <kvalo@kernel.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull request: mt76 2022-02-23
Date: Thu, 24 Feb 2022 11:46:33 +0200 [thread overview]
Message-ID: <87k0dkvbpi.fsf@kernel.org> (raw)
In-Reply-To: <e7f282ef-7dce-7d65-ae15-d26fb8fb6773@nbd.name> (Felix Fietkau's message of "Wed, 23 Feb 2022 14:53:59 +0100")
Felix Fietkau <nbd@nbd.name> writes:
> here's my second pull request for 5.18
>
> - Felix
>
> The following changes since commit a0061be4e54b52e5e4ff179c3f817107ddbb2830:
>
> rtw88: change rtw_info() to proper message level (2022-02-22 17:31:13 +0200)
>
> are available in the Git repository at:
>
> https://github.com/nbd168/wireless tags/mt76-for-kvalo-2022-02-23
>
> for you to fetch changes up to f8629a7a5772747b6aaf4e672f7b9729209e34a5:
>
> mt76: mt7915: simplify conditional (2022-02-23 14:53:00 +0100)
>
> ----------------------------------------------------------------
> mt76 patches for 5.18
>
> - bugfixes
> - mt7915 thermal management improvements
> - SAR support for more mt76 drivers
> - mt7986 wmac support on mt7915
>
> ----------------------------------------------------------------
Please switch to use my new email address: kvalo@kernel.org
This has new warnings with GCC 11.1:
drivers/net/wireless/mediatek/mt76/mt7915/soc.c: In function 'mt7986_wmac_gpio_setup':
drivers/net/wireless/mediatek/mt76/mt7915/soc.c:197:19: error: implicit declaration of function 'devm_pinctrl_get'; did you mean 'of_pinctrl_get'? [-Werror=implicit-function-declaration]
197 | pinctrl = devm_pinctrl_get(dev->mt76.dev);
| ^~~~~~~~~~~~~~~~
| of_pinctrl_get
drivers/net/wireless/mediatek/mt76/mt7915/soc.c:197:17: error: assignment to 'struct pinctrl *' from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
197 | pinctrl = devm_pinctrl_get(dev->mt76.dev);
| ^
drivers/net/wireless/mediatek/mt76/mt7915/soc.c:201:25: error: implicit declaration of function 'pinctrl_lookup_state' [-Werror=implicit-function-declaration]
201 | state = pinctrl_lookup_state(pinctrl, "default");
| ^~~~~~~~~~~~~~~~~~~~
drivers/net/wireless/mediatek/mt76/mt7915/soc.c:201:23: error: assignment to 'struct pinctrl_state *' from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
201 | state = pinctrl_lookup_state(pinctrl, "default");
| ^
drivers/net/wireless/mediatek/mt76/mt7915/soc.c:206:23: error: assignment to 'struct pinctrl_state *' from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
206 | state = pinctrl_lookup_state(pinctrl, "dbdc");
| ^
drivers/net/wireless/mediatek/mt76/mt7915/soc.c:212:15: error: implicit declaration of function 'pinctrl_select_state' [-Werror=implicit-function-declaration]
212 | ret = pinctrl_select_state(pinctrl, state);
| ^~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-02-24 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 13:53 pull request: mt76 2022-02-23 Felix Fietkau
2022-02-24 9:46 ` Kalle Valo [this message]
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=87k0dkvbpi.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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).