All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: <tony0620emma@gmail.com>, <kvalo@kernel.org>
Cc: <linux-wireless@vger.kernel.org>, <usama.anjum@collabora.com>,
	<phhuang@realtek.com>
Subject: [PATCH 0/3] rtw88: some fixes of hw_scan
Date: Fri, 21 Jan 2022 15:08:10 +0800	[thread overview]
Message-ID: <20220121070813.9656-1-pkshih@realtek.com> (raw)

Since patch 2/3 and 3/3 is based on the first patch sent by Muhammad
https://lore.kernel.org/linux-wireless/YcWK1jxnd3vGdmCq@debian-BULLSEYE-live-builder-AMD64/
I put them together in this patchset, so we don't miss it.

The second patch is to enter idle mode by driver after hw_scan, and then
it can save more power. Third patch is to fix memory overrun and leak that
will lead kernel crash.

Muhammad Usama Anjum (1):
  rtw88: check for validity before using a pointer

Po-Hao Huang (2):
  rtw88: fix idle mode flow for hw scan
  rtw88: fix memory overrun and memory leak during hw_scan

 drivers/net/wireless/realtek/rtw88/fw.c       | 40 ++++++++++++++-----
 drivers/net/wireless/realtek/rtw88/mac80211.c |  5 ++-
 drivers/net/wireless/realtek/rtw88/main.c     | 16 +++++++-
 drivers/net/wireless/realtek/rtw88/main.h     |  4 +-
 4 files changed, 53 insertions(+), 12 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-01-21  7:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21  7:08 Ping-Ke Shih [this message]
2022-01-21  7:08 ` [PATCH 1/3] rtw88: check for validity before using a pointer Ping-Ke Shih
2022-01-31 15:47   ` Kalle Valo
2022-01-21  7:08 ` [PATCH 2/3] rtw88: fix idle mode flow for hw scan Ping-Ke Shih
2022-01-21  7:08 ` [PATCH 3/3] rtw88: fix memory overrun and memory leak during hw_scan 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=20220121070813.9656-1-pkshih@realtek.com \
    --to=pkshih@realtek.com \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=phhuang@realtek.com \
    --cc=tony0620emma@gmail.com \
    --cc=usama.anjum@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.