From: Ping-Ke Shih <pkshih@realtek.com>
To: Nithyanantham Paramasivam <nithyanantham.paramasivam@oss.qualcomm.com>
Cc: "ath12k@lists.infradead.org" <ath12k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH ath-next v2 2/3] wifi: ath12k: Fix TX status reporting to mac80211 when offload is enabled
Date: Fri, 18 Jul 2025 13:28:29 +0000 [thread overview]
Message-ID: <7859082aeea642e2a3fa3a2829404b55@realtek.com> (raw)
In-Reply-To: <CAD1Z1JK1wnCTeObYAHALkxDVFm0kx=7r4urtA4S0XorLNOPKfg@mail.gmail.com>
Nithyanantham Paramasivam <nithyanantham.paramasivam@oss.qualcomm.com> wrote:
> On Fri, Jul 18, 2025 at 2:45 PM Ping-Ke Shih <pkshih@realtek.com> wrote:
> >
> > > @@ -578,6 +579,8 @@ ath12k_dp_tx_htt_tx_complete_buf(struct ath12k_base *ab,
> > > struct ath12k *ar;
> > > struct sk_buff *msdu = desc_params->skb;
> > > s32 noise_floor;
> > > + struct ieee80211_tx_status status = { 0 };
> >
> > With '= {}', no matter how the struct changes, you don't need to change the
> > code accordingly.
> >
>
> Both ={} and = {0} achieve the same result, right?
Yes.
However, in some cases, it might cause compiler error. But I forgot the cases,
even I can't reproduce the error now. Sorry for the noise.
next prev parent reply other threads:[~2025-07-18 13:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 2:55 [PATCH ath-next v2 0/3] wifi: ath12k: Add 802.11 encap/decap offload support Nithyanantham Paramasivam
2025-07-18 2:55 ` [PATCH ath-next v2 1/3] wifi: ath12k: Fix the handling of TX packets in Ethernet mode Nithyanantham Paramasivam
2025-07-18 17:16 ` Jeff Johnson
2025-07-18 2:55 ` [PATCH ath-next v2 2/3] wifi: ath12k: Fix TX status reporting to mac80211 when offload is enabled Nithyanantham Paramasivam
2025-07-18 9:12 ` Ping-Ke Shih
2025-07-18 12:56 ` Nithyanantham Paramasivam
2025-07-18 13:28 ` Ping-Ke Shih [this message]
2025-07-18 13:47 ` Nithyanantham Paramasivam
2025-07-18 13:55 ` Jeff Johnson
2025-07-18 14:05 ` Nithyanantham Paramasivam
2025-07-18 16:30 ` Jeff Johnson
2025-07-18 2:55 ` [PATCH ath-next v2 3/3] wifi: ath12k: Advertise encapsulation/decapsulation offload support to mac80211 Nithyanantham Paramasivam
2025-07-18 16:11 ` [PATCH ath-next v2 0/3] wifi: ath12k: Add 802.11 encap/decap offload support Vasanthakumar Thiagarajan
2025-07-19 16:22 ` 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=7859082aeea642e2a3fa3a2829404b55@realtek.com \
--to=pkshih@realtek.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nithyanantham.paramasivam@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