From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: nbd@nbd.name, linux-wireless@vger.kernel.org,
lorenzo.bianconi@redhat.com, shayne.chen@mediatek.com,
ryder.lee@mediatek.com
Subject: Re: [PATCH] wifi: mt76: mt7915: workaround too long expansion sparse warnings
Date: Wed, 20 Mar 2024 10:13:52 +0100 [thread overview]
Message-ID: <Zfqo0I3CpWE6tHTh@lore-desk> (raw)
In-Reply-To: <87h6h12rrg.fsf@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
> Lorenzo Bianconi <lorenzo@kernel.org> writes:
>
> > Fix the following sparse warnings:
> >
> > drivers/net/wireless/mediatek/mt76/mt7915/debugfs.c:1133:29: error: too long token expansion
> > drivers/net/wireless/mediatek/mt76/mt7915/debugfs.c:1133:29: error: too long token expansion
> > drivers/net/wireless/mediatek/mt76/mt7915/debugfs.c:1133:29: error: too long token expansion
> > drivers/net/wireless/mediatek/mt76/mt7915/debugfs.c:1133:29: error: too long token expansion
> >
> > No functional changes, compile tested only.
> >
> > Fixes: e3296759f347 ("wifi: mt76: mt7915: enable per bandwidth power limit support")
> > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
>
> Thanks Lorenzo! Could I take this directly to wireless-next? We are very
> close of being sparse clean in the wireless subsystem, there are just
> few warnings left ath drivers.
sure, I am fine with it.
@Felix?
Regards,
Lorenzo
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-03-20 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 15:12 [PATCH] wifi: mt76: mt7915: workaround too long expansion sparse warnings Lorenzo Bianconi
2024-03-19 16:17 ` Johannes Berg
2024-03-20 9:10 ` Kalle Valo
2024-03-20 9:13 ` Lorenzo Bianconi [this message]
2024-03-20 9:18 ` Felix Fietkau
2024-03-20 9:49 ` Kalle Valo
2024-03-21 15:09 ` 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=Zfqo0I3CpWE6tHTh@lore-desk \
--to=lorenzo@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=shayne.chen@mediatek.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