From: Ping-Ke Shih <pkshih@realtek.com>
To: "Rafael Alejandro Díaz Cruz" <rafad900@gmail.com>
Cc: "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 rtw-next v5] wifi: rtl8xxxu: Use local 'dev' variable for dev_warn()
Date: Wed, 19 Aug 2026 06:49:53 +0000 [thread overview]
Message-ID: <704a15b7526d479f8b5a644acb8ff534@realtek.com> (raw)
In-Reply-To: <CALp66yG9PdUmrs1QS-shG3=gchxD2QOYX065tNVq4zrTCZLdwA@mail.gmail.com>
Please plain text only.
Rafael Alejandro Díaz Cruz <rafad900@gmail.com> wrote:
> There are multiple places where the dev variable would only be used once.
> I was hoping to only adjust the function calls that had &priv->udev->dev
> more than once to avoid redundancy.
I didn't get this point. As I come back to your first version [1], you
didn't mention and do this.
[1] https://patchwork.kernel.org/project/linux-wireless/patch/20260816180857.4122090-1-rafad900@gmail.com/
> But I'm a little confused because you mentioned in a previous patch:
> " If it is worth to do, please convert all of them. " I was hoping to
> change all the dev_warn(), dev_err(), dev_info(), dev_dbg() since they
> all use the same &priv->udev->dev but I was going to submit different
> patches for each one. Perhaps I should take another approach.
> I guess this change might not actually be worth the trouble.
I didn't actually know your goal, so no idea if this is worth to stir
the code.
> Thanks for your patience and help with this patch. I'll put this off
> until I find something else to contribute with it.
I dropped this from patchwork then.
prev parent reply other threads:[~2026-08-19 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 19:34 [PATCH rtw-next v5] wifi: rtl8xxxu: Use local 'dev' variable for dev_warn() rafad900
2026-08-19 0:22 ` Ping-Ke Shih
[not found] ` <CALp66yG9PdUmrs1QS-shG3=gchxD2QOYX065tNVq4zrTCZLdwA@mail.gmail.com>
2026-08-19 6:49 ` 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=704a15b7526d479f8b5a644acb8ff534@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 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.