From: Kalle Valo <kvalo@kernel.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH for-6.2 3/3] wifi: brcmfmac: change cfg80211_set_channel() name and signature
Date: Mon, 09 Jan 2023 17:50:55 +0200 [thread overview]
Message-ID: <87pmbnhfkw.fsf@kernel.org> (raw)
In-Reply-To: <20230103124117.271988-4-arend.vanspriel@broadcom.com> (Arend van Spriel's message of "Tue, 3 Jan 2023 13:41:17 +0100")
Arend van Spriel <arend.vanspriel@broadcom.com> writes:
> The function cfg80211_set_channel() is an static function in brcmfmac
> but the name is misleading. Hence rename it with 'brcmf' prefix. Also
> changing the parameters to avoid additional conversions.
>
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
If I understood correctly this patch 3 is for wireless-next. So adding a
reminder for myself to _not_ take this to wireless tree :)
(I wish patchwork would have a support for offline notes so I would not
need to send emails like this)
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-01-09 15:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 12:41 [PATCH for-6.2 0/3] wifi: brcmfmac: regression fixes Arend van Spriel
2023-01-03 12:41 ` [PATCH for-6.2 1/3] wifi: brcmfmac: avoid handling disabled channels for survey dump Arend van Spriel
2023-01-03 19:15 ` Stefan Wahren
2023-01-03 19:44 ` Arend van Spriel
2023-01-16 11:26 ` Kalle Valo
2023-01-03 12:41 ` [PATCH for-6.2 2/3] wifi: brcmfmac: avoid NULL-deref in survey dump for 2G only device Arend van Spriel
2023-01-03 13:36 ` Arend van Spriel
2023-01-03 12:41 ` [PATCH for-6.2 3/3] wifi: brcmfmac: change cfg80211_set_channel() name and signature Arend van Spriel
2023-01-09 15:50 ` Kalle Valo [this message]
2023-01-09 17:38 ` Arend Van Spriel
2023-02-13 16:54 ` 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=87pmbnhfkw.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=arend.vanspriel@broadcom.com \
--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.