From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Arnd Bergmann <arnd@arndb.de>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: iwlegacy: avoid size increase
Date: Tue, 4 Mar 2025 17:18:39 +0100 [thread overview]
Message-ID: <20250304161839.GA67578@wp.pl> (raw)
In-Reply-To: <20250304144210.997531-1-arnd@kernel.org>
On Tue, Mar 04, 2025 at 03:42:07PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> My previous patch caused a slight code size increase when DEBUG_FS is disabled,
> as Stanislaw Gruszka pointed out.
>
> Fix this with an added IS_ENABLED() check.
>
> Fixes: cf6b9ba172dd ("wifi: iwlegacy: don't warn for unused variables with DEBUG_FS=n")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> Ideally this would be folded into my original fix. If that's not possible,
> please apply on top.
Acked-by: Stanislaw Gruszka <stf_xl@wp.pl>
> drivers/net/wireless/intel/iwlegacy/4965-rs.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/wireless/intel/iwlegacy/4965-rs.c b/drivers/net/wireless/intel/iwlegacy/4965-rs.c
> index f754fb979546..0e5130d1fccd 100644
> --- a/drivers/net/wireless/intel/iwlegacy/4965-rs.c
> +++ b/drivers/net/wireless/intel/iwlegacy/4965-rs.c
> @@ -2495,6 +2495,9 @@ il4965_rs_dbgfs_set_mcs(struct il_lq_sta *lq_sta, u32 * rate_n_flags, int idx)
> u8 valid_tx_ant;
> u8 ant_sel_tx;
>
> + if (!IS_ENABLED(CONFIG_MAC80211_DEBUGFS))
> + return;
> +
> il = lq_sta->drv;
> valid_tx_ant = il->hw_params.valid_tx_ant;
> if (lq_sta->dbg_fixed_rate) {
> --
> 2.39.5
>
prev parent reply other threads:[~2025-03-04 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 14:42 [PATCH] wifi: iwlegacy: avoid size increase Arnd Bergmann
2025-03-04 16:18 ` Stanislaw Gruszka [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=20250304161839.GA67578@wp.pl \
--to=stf_xl@wp.pl \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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.