From: Ping-Ke Shih <pkshih@realtek.com>
To: Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: NIPA/wifibot disappeared
Date: Mon, 22 Jun 2026 07:45:58 +0000 [thread overview]
Message-ID: <c7363a78c6324d519651c7729617b725@realtek.com> (raw)
In-Reply-To: <8f08a690242483a0c1026e7b006f48c9c01c6f30.camel@sipsolutions.net>
Hi Johannes,
Johannes Berg <johannes@sipsolutions.net> wrote:
> It's on the netdev config, so perhaps a little pickier than it used to
> be.
Not sure how it considers -next tree. My patch with subject
"[PATCH rtw-next] wifi: rtl8xxxu: 8723bu: ..." is treated as non-next tree [1].
Could you help to update NIPA configuration? Or should I change to other
proper tree selection of subject prefix?
[1] https://patchwork.kernel.org/project/linux-wireless/patch/20260622015439.9621-1-pkshih@realtek.com/
Ping-Ke
prev parent reply other threads:[~2026-06-22 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 10:52 NIPA/wifibot disappeared Johannes Berg
2026-06-18 11:50 ` Johannes Berg
2026-06-22 7:45 ` 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=c7363a78c6324d519651c7729617b725@realtek.com \
--to=pkshih@realtek.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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