From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>
Subject: RE: [PATCH v3 5/5] wifi: rtl8xxxu: Use dev_info instead of pr_info
Date: Mon, 31 Oct 2022 01:09:07 +0000 [thread overview]
Message-ID: <9dd7b9634d754afb97a70bd5bf0fadc0@realtek.com> (raw)
In-Reply-To: <f5ceeb63-bfd2-0fe5-c88b-2bc4c9c7c46a@gmail.com>
> -----Original Message-----
> From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> Sent: Saturday, October 29, 2022 12:40 AM
> To: linux-wireless@vger.kernel.org
> Cc: Jes Sorensen <Jes.Sorensen@gmail.com>
> Subject: [PATCH v3 5/5] wifi: rtl8xxxu: Use dev_info instead of pr_info
>
> Replace two instances of bare pr_info with dev_info.
>
> Also make their messages a little more informative.
>
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>
> ---
> v3:
> - No change.
>
> v2:
> - No change.
> ---
[...]
next prev parent reply other threads:[~2022-10-31 1:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 16:30 [PATCH v3 1/5] wifi: rtl8xxxu: Add central frequency offset tracking Bitterblue Smith
2022-10-28 16:36 ` [PATCH v3 2/5] wifi: rtl8xxxu: Fix the CCK RSSI calculation Bitterblue Smith
2022-10-31 1:07 ` Ping-Ke Shih
2022-10-28 16:37 ` [PATCH v3 3/5] wifi: rtl8xxxu: Recognise all possible chip cuts Bitterblue Smith
2022-10-31 1:08 ` Ping-Ke Shih
2022-10-28 16:38 ` [PATCH v3 4/5] wifi: rtl8xxxu: Set IEEE80211_HW_SUPPORT_FAST_XMIT Bitterblue Smith
2022-10-31 1:08 ` Ping-Ke Shih
2022-10-28 16:40 ` [PATCH v3 5/5] wifi: rtl8xxxu: Use dev_info instead of pr_info Bitterblue Smith
2022-10-31 1:09 ` Ping-Ke Shih [this message]
2022-11-01 11:11 ` Kalle Valo
2022-11-01 17:49 ` Bitterblue Smith
2022-10-31 1:07 ` [PATCH v3 1/5] wifi: rtl8xxxu: Add central frequency offset tracking Ping-Ke Shih
2022-11-01 11:09 ` Kalle Valo
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=9dd7b9634d754afb97a70bd5bf0fadc0@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.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.