ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Antipov <dmantipov@yandex.ru>
To: Kalle Valo <kvalo@kernel.org>
Cc: Baochen Qiang <quic_bqiang@quicinc.com>,
	Jeff Johnson <quic_jjohnson@quicinc.com>,
	ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	lvc-project@linuxtesting.org
Subject: Re: [PATCH] wifi: ath11k: fix few -Wmaybe-uninitialized warnings
Date: Wed, 28 Feb 2024 17:13:21 +0300	[thread overview]
Message-ID: <2b90c19d-e2b7-4dd9-8656-dbc6e7fd1d2c@yandex.ru> (raw)
In-Reply-To: <875xy8k7rt.fsf@kernel.org>

On 2/28/24 17:01, Kalle Valo wrote:

> 
> Did you verify that the warnings are valid?
> 

Well, hopefully yes. Just in case, gcc 13.2.1 issues an
exactly the same set of -Wmaybe-uninitialized warnings.

Dmitry



  reply	other threads:[~2024-02-28 14:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 13:14 [PATCH] wifi: ath11k: fix few -Wmaybe-uninitialized warnings Dmitry Antipov
2024-02-28 14:01 ` Kalle Valo
2024-02-28 14:13   ` Dmitry Antipov [this message]
2024-02-28 15:54 ` Jeff Johnson
2024-02-29  8:40   ` [PATCH 1/3] [v2] wifi: ath11k: use ath11k_mac_get_ar_by_pdev_id() consistently Dmitry Antipov
2024-02-29  8:40     ` [PATCH 2/3] [v2] wifi: ath11k: handle unknown scan state in ath11k_mac_op_remain_on_channel() Dmitry Antipov
2024-02-29 20:18       ` Jeff Johnson
2024-02-29  8:40     ` [PATCH 3/3] [v2] wifi: ath11k: fix few -Wmaybe-uninitialized warnings Dmitry Antipov
2024-02-29 21:00       ` Jeff Johnson
2024-02-29 20:10     ` [PATCH 1/3] [v2] wifi: ath11k: use ath11k_mac_get_ar_by_pdev_id() consistently 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=2b90c19d-e2b7-4dd9-8656-dbc6e7fd1d2c@yandex.ru \
    --to=dmantipov@yandex.ru \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=quic_bqiang@quicinc.com \
    --cc=quic_jjohnson@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