From: Kalle Valo <kvalo@kernel.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"John W . Linville" <linville@tuxdriver.com>,
Seth Forshee <sforshee@kernel.org>,
"Pieter-Paul Giesberts" <pieterpg@broadcom.com>,
<linux-wireless@vger.kernel.org>, <brcm80211@lists.linux.dev>,
<brcm80211-dev-list.pdl@broadcom.com>,
<linux-trace-kernel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] brcm80211: BRCM_TRACING should depend on TRACING
Date: Tue, 24 Sep 2024 16:35:55 +0300 [thread overview]
Message-ID: <874j659nt0.fsf@kernel.org> (raw)
In-Reply-To: <19224165b90.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> (Arend Van Spriel's message of "Tue, 24 Sep 2024 14:51:38 +0200")
Arend Van Spriel <arend.vanspriel@broadcom.com> writes:
> On September 24, 2024 2:09:35 PM Geert Uytterhoeven
> <geert@linux-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@broadcom.com>
I'm planning to take this to wireless and I'll add 'wifi:' to the title.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-09-24 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 12:09 [PATCH] brcm80211: BRCM_TRACING should depend on TRACING Geert Uytterhoeven
2024-09-24 12:51 ` Arend Van Spriel
2024-09-24 13:35 ` Kalle Valo [this message]
2024-10-17 14:23 ` wifi: " 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=874j659nt0.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pieterpg@broadcom.com \
--cc=sforshee@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.