linux-kernel - Re: [PATCH] brcm80211: BRCM_TRACING should depend on TRACING

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19224165b90.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com>
Date: Tue, 24 Sep 2024 14:51:38 +0200
From: Arend Van Spriel <arend.vanspriel@...adcom.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>, Kalle Valo <kvalo@...nel.org>, "John W . Linville" <linville@...driver.com>, Seth Forshee <sforshee@...nel.org>, "Pieter-Paul Giesberts" <pieterpg@...adcom.com>
CC: <linux-wireless@...r.kernel.org>, <brcm80211@...ts.linux.dev>, <brcm80211-dev-list.pdl@...adcom.com>, <linux-trace-kernel@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] brcm80211: BRCM_TRACING should depend on TRACING

On September 24, 2024 2:09:35 PM Geert Uytterhoeven <geert@...ux-m68k.org> 
wrote:

> When tracing is disabled, there is no point in asking the user about
> enabling Broadcom wireless device tracing.
>
> Fixes: f5c4f10852d42012 ("brcm80211: Allow trace support to be enabled 
> separately from debug")
Acked-by: Arend van Spriel <arend.vanspriel@...adcom.com>
> Signed-off-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> ---
> drivers/net/wireless/broadcom/brcm80211/Kconfig | 1 +
> 1 file changed, 1 insertion(+)