From: Vasanthakumar Thiagarajan <quic_vthiagar@quicinc.com>
To: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>, <jjohnson@kernel.org>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] wifi: ath10k: clean up structure initialization
Date: Thu, 30 Oct 2025 23:56:02 +0530 [thread overview]
Message-ID: <1c8af83c-ec93-94ef-e309-a911064507a9@quicinc.com> (raw)
In-Reply-To: <20251030130023.1836808-1-zhongqiu.han@oss.qualcomm.com>
On 10/30/2025 6:30 PM, Zhongqiu Han wrote:
> This patchset simplifies structure initialization in ath10k by replacing
> explicit memset() calls with zero initializers (`= {}`) for local
> variables.
>
> Patch 1 updates the initialization of `pm_qos_request` in
> ath10k_download_fw().
>
> Patch 2 updates the initialization of `bmi_target_info` in
> ath10k_core_probe_fw().
>
> These changes improve code clarity and efficiency by avoiding unnecessary
> runtime memset calls.
>
> Zhongqiu Han (2):
> wifi: ath10k: use = {} to initialize pm_qos_request instead of memset
> wifi: ath10k: use = {} to initialize bmi_target_info instead of memset
>
> drivers/net/wireless/ath/ath10k/core.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
Branch name is missing, with that addressed
Reviewed-by: Vasanthakumar Thiagarajan <vasanthakumar.thiagarajan@oss.qualcomm.com>
next prev parent reply other threads:[~2025-10-30 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 13:00 Zhongqiu Han
2025-10-30 13:00 ` [PATCH 1/2] wifi: ath10k: use = {} to initialize pm_qos_request instead of memset Zhongqiu Han
2025-10-30 13:00 ` [PATCH 2/2] wifi: ath10k: use = {} to initialize bmi_target_info " Zhongqiu Han
2025-10-30 18:26 ` Vasanthakumar Thiagarajan [this message]
2025-10-30 21:57 ` [PATCH 0/2] wifi: ath10k: clean up structure initialization 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=1c8af83c-ec93-94ef-e309-a911064507a9@quicinc.com \
--to=quic_vthiagar@quicinc.com \
--cc=ath10k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zhongqiu.han@oss.qualcomm.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
all inboxes | Powered by JetHome®