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 v2] wifi: rtl8xxxu: Use local 'dev' variable for dev_warn()
Date: Mon, 17 Aug 2026 08:31:02 +0000 [thread overview]
Message-ID: <f6efe2a8bf464a3cb4e53fdac161f6e7@realtek.com> (raw)
In-Reply-To: <20260817052250.358796-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.
> This follows the logging pattern used in most of
> rtl8xxxu files.
>
> Signed-off-by: Rafael Alejandro Diaz Cruz <rafad900@gmail.com>
NIPA reported many fail and warning items [1].
The tree selection should be rtw-next. e.g. [PATCH rtw-next v3]
[1] https://patchwork.kernel.org/project/linux-wireless/patch/20260817052250.358796-1-rafad900@gmail.com/
prev parent reply other threads:[~2026-08-17 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 5:22 [PATCH v2] wifi: rtl8xxxu: Use local 'dev' variable for dev_warn() rafad900
2026-08-17 8:31 ` 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=f6efe2a8bf464a3cb4e53fdac161f6e7@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.