From: Kalle Valo <kvalo@kernel.org>
To: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
Subject: Re: [PATCH 1/2] wifi: ath11k: rename the wmi_sc naming convention to wmi_ab
Date: Wed, 18 Oct 2023 08:34:10 +0000 (UTC) [thread overview]
Message-ID: <169761804880.48072.5715328837742123686.kvalo@kernel.org> (raw)
In-Reply-To: <20231014032650.32605-2-quic_periyasa@quicinc.com>
Karthikeyan Periyasamy <quic_periyasa@quicinc.com> wrote:
> In WMI layer module, the identifier wmi_sc is used to represent
> an instance of ath11k_wmi_base structure. However, within ath11k,
> the convention is to use "ab" to represent an SoC "base" struct.
> So change the all instances of wmi_sc to wmi_ab.
>
> Compile tested only.
>
> Signed-off-by: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
> Acked-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
2 patches applied to ath-next branch of ath.git, thanks.
265c038ac9c2 wifi: ath11k: rename the wmi_sc naming convention to wmi_ab
2e66190e0d87 wifi: ath11k: rename the sc naming convention to ab
--
https://patchwork.kernel.org/project/linux-wireless/patch/20231014032650.32605-2-quic_periyasa@quicinc.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2023-10-18 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 3:26 [PATCH 0/2] wifi: ath11k: rename the variable naming convention Karthikeyan Periyasamy
2023-10-14 3:26 ` [PATCH 1/2] wifi: ath11k: rename the wmi_sc naming convention to wmi_ab Karthikeyan Periyasamy
2023-10-16 15:06 ` Jeff Johnson
2023-10-18 8:34 ` Kalle Valo [this message]
2023-10-14 3:26 ` [PATCH 2/2] wifi: ath11k: rename the sc naming convention to ab Karthikeyan Periyasamy
2023-10-16 15:06 ` Jeff Johnson
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=169761804880.48072.5715328837742123686.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_periyasa@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).