From: Ping-Ke Shih <pkshih@realtek.com>
To: rafad900 <rafad900@gmail.com>,
"Jes.Sorensen@gmail.com" <Jes.Sorensen@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtl8xxxu: Adjust logging pattern
Date: Mon, 17 Aug 2026 03:16:45 +0000 [thread overview]
Message-ID: <adb34509bb6c4767bd1e1f24cc99a62d@realtek.com> (raw)
In-Reply-To: <20260816180857.4122090-1-rafad900@gmail.com>
rafad900 <rafad900@gmail.com> wrote:
> To ensure consistent patterns, the device struct was
> defined and used when dev_warn() is called within
> rtl8188eu_rx_iqk_path_a().
> This follows the logging pattern used by all the
> other functions defined in the file.
>
> Signed-off-by: rafad900 <rafad900@gmail.com>
Please use your real name.
The subject can explicitly point out that you are adjusting to use a
local 'dev' variable for dev_warn().
> ---
> drivers/net/wireless/realtek/rtl8xxxu/8188e.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/realtek/rtl8xxxu/8188e.c
> b/drivers/net/wireless/realtek/rtl8xxxu/8188e.c
> index fea5aec9ced9..4a64633b2da3 100644
> --- a/drivers/net/wireless/realtek/rtl8xxxu/8188e.c
> +++ b/drivers/net/wireless/realtek/rtl8xxxu/8188e.c
> @@ -643,6 +643,7 @@ static int rtl8188eu_iqk_path_a(struct rtl8xxxu_priv *priv)
>
> static int rtl8188eu_rx_iqk_path_a(struct rtl8xxxu_priv *priv)
> {
> + struct device *dev = &priv->udev->dev;
> u32 reg_ea4, reg_eac, reg_e94, reg_e9c, val32;
> int result = 0;
>
> @@ -740,7 +741,7 @@ static int rtl8188eu_rx_iqk_path_a(struct rtl8xxxu_priv *priv)
> ((reg_eac & 0x03ff0000) != 0x00360000))
> result |= 0x02;
> else
> - dev_warn(&priv->udev->dev, "%s: Path A RX IQK failed!\n",
> + dev_warn(dev, "%s: Path A RX IQK failed!\n",
The counts of individual use case are:
$ git grep "dev_warn(&priv->udev->dev" drivers/net/wireless/realtek/rtl8xxxu/ | wc -l
19
$ git grep "dev_warn(dev" drivers/net/wireless/realtek/rtl8xxxu/ | wc -l
35
If it is worth to do, please convert all of them.
> __func__);
>
> out:
> --
> 2.43.0
>
prev parent reply other threads:[~2026-08-17 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 18:08 [PATCH] wifi: rtl8xxxu: Adjust logging pattern rafad900
2026-08-17 3:16 ` Ping-Ke Shih [this message]
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=adb34509bb6c4767bd1e1f24cc99a62d@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rafad900@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox