linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Kalle Valo <kvalo@kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH 2/3] [v5] wifi: rtw89: cleanup rtw89_iqk_info and related code
Date: Wed, 14 Jun 2023 07:05:25 +0000	[thread overview]
Message-ID: <2cacf4bda2214cef8623ceec5bfbafe3@realtek.com> (raw)
In-Reply-To: <20230614051116.20968-2-dmantipov@yandex.ru>



> -----Original Message-----
> From: Dmitry Antipov <dmantipov@yandex.ru>
> Sent: Wednesday, June 14, 2023 1:11 PM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: Kalle Valo <kvalo@kernel.org>; linux-wireless@vger.kernel.org; Dmitry Antipov <dmantipov@yandex.ru>
> Subject: [PATCH 2/3] [v5] wifi: rtw89: cleanup rtw89_iqk_info and related code
> 
> Drop useless '_iqk_track()' and 'rtw8852a_iqk_track()' (they
> just change 'thermal_rek_en' field which is set but unused
> and so removed as well) functions, set but unused 'kcount'
> field of 'struct rtw89_iqk_info', and convert 'thermal' to
> local variables where appropriate (it doesn't need to have
> longer storage duration because it is actually used for the
> debugging purposes only).
> 
> Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>

Acked-by: Ping-Ke Shih <pkshih@realtek.com>

[...]


  reply	other threads:[~2023-06-14  7:06 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  8:33 [PATCH] wifi: rtw89: cleanup private data structures Dmitry Antipov
2023-06-06 14:08 ` [PATCH 1/2] " Dmitry Antipov
2023-06-06 14:08   ` [PATCH 2/2] wifi: rtw89: cleanup rtw89_iqk_info and related code Dmitry Antipov
2023-06-08  0:40     ` Ping-Ke Shih
2023-06-08  7:45     ` [PATCH] [v2] " Dmitry Antipov
2023-06-08  8:03       ` Ping-Ke Shih
2023-06-08  8:24       ` [PATCH 1/2] [v3] wifi: rtw89: cleanup private data structures Dmitry Antipov
2023-06-08  8:24         ` [PATCH 2/2] [v3] wifi: rtw89: cleanup rtw89_iqk_info and related code Dmitry Antipov
2023-06-08  8:42           ` Ping-Ke Shih
2023-06-13  8:23           ` Kalle Valo
2023-06-08  8:41         ` [PATCH 1/2] [v3] wifi: rtw89: cleanup private data structures Ping-Ke Shih
2023-06-13  8:38         ` Kalle Valo
2023-06-13  8:56           ` Dmitry Antipov
2023-06-13  9:11             ` Ping-Ke Shih
2023-06-13  9:12             ` Kalle Valo
2023-06-13 10:01             ` [PATCH 1/3] [v4] " Dmitry Antipov
2023-06-13 10:01               ` [PATCH 2/3] [v4] wifi: rtw89: cleanup rtw89_iqk_info and related code Dmitry Antipov
2023-06-14  2:54                 ` Ping-Ke Shih
2023-06-13 10:01               ` [PATCH 3/3] wifi: rtw89: fix typo Dmitry Antipov
2023-06-14  2:56                 ` Ping-Ke Shih
2023-06-14  5:11                 ` [PATCH 1/3] [v5] wifi: rtw89: cleanup private data structures Dmitry Antipov
2023-06-14  5:11                   ` [PATCH 2/3] [v5] wifi: rtw89: cleanup rtw89_iqk_info and related code Dmitry Antipov
2023-06-14  7:05                     ` Ping-Ke Shih [this message]
2023-06-14  5:11                   ` [PATCH 3/3] [v5] wifi: rtw89: fix spelling typo of IQK debug messages Dmitry Antipov
2023-06-14  7:06                     ` Ping-Ke Shih
2023-06-14  8:15                     ` [PATCH 1/3] [v6] wifi: rtw89: cleanup private data structures Dmitry Antipov
2023-06-14  8:15                       ` [PATCH 2/3] [v6] wifi: rtw89: cleanup rtw89_iqk_info and related code Dmitry Antipov
2023-06-14  8:15                       ` [PATCH 3/3] [v6] wifi: rtw89: fix spelling typo of IQK debug messages Dmitry Antipov
2023-06-14  8:22                         ` Ping-Ke Shih
2023-06-15  7:47                       ` [PATCH 1/3] [v6] wifi: rtw89: cleanup private data structures Kalle Valo
2023-06-14  7:04                   ` [PATCH 1/3] [v5] " Ping-Ke Shih
2023-06-14  2:50               ` [PATCH 1/3] [v4] " Ping-Ke Shih
2023-06-08  0:31   ` [PATCH 1/2] " Ping-Ke Shih
2023-06-08  0:23 ` [PATCH] " Ping-Ke Shih

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=2cacf4bda2214cef8623ceec5bfbafe3@realtek.com \
    --to=pkshih@realtek.com \
    --cc=dmantipov@yandex.ru \
    --cc=kvalo@kernel.org \
    --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 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 NNTP newsgroup(s).