All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Lorenzo Bianconi <lorenzo@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 11:10:11 +0200	[thread overview]
Message-ID: <87h6h12rrg.fsf@kernel.org> (raw)
In-Reply-To: <5457b92e41909dd75ab3db7a0e9ec372b917a386.1710858172.git.lorenzo@kernel.org> (Lorenzo Bianconi's message of "Tue, 19 Mar 2024 16:12:47 +0100")

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.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  parent reply	other threads:[~2024-03-20  9:10 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 [this message]
2024-03-20  9:13   ` Lorenzo Bianconi
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=87h6h12rrg.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=lorenzo@kernel.org \
    --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 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.