From: 王颢 <howard_wang@realsil.com.cn>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"pro_nic_dpdk@realtek.com" <pro_nic_dpdk@realtek.com>
Subject: 回复: [PATCH v2 01/12] net/r8169: fix NULL pointer dereference in rtl8168fp_ops
Date: Thu, 12 Feb 2026 05:51:51 +0000 [thread overview]
Message-ID: <a422d66b5d284415a399bbe8ca5f2b7c@realsil.com.cn> (raw)
In-Reply-To: <20260211134235.258f347c@phoenix.local>
Thanks. Since I need to send a v3 to address comments on another patch in this series, I will include this updated commit message in v3.
-----邮件原件-----
发件人: Stephen Hemminger <stephen@networkplumber.org>
发送时间: 2026年2月12日 5:43
收件人: 王颢 <howard_wang@realsil.com.cn>
抄送: dev@dpdk.org; pro_nic_dpdk@realtek.com
主题: Re: [PATCH v2 01/12] net/r8169: fix NULL pointer dereference in rtl8168fp_ops
External mail : This email originated from outside the organization. Do not reply, click links, or open attachments unless you recognize the sender and know the content is safe.
On Tue, 10 Feb 2026 13:55:00 +0800
Howard Wang <howard_wang@realsil.com.cn> wrote:
> Fixes: d9ee71b5f1bc ("net/r8169: support RTL8168 series")
>
> Signed-off-by: Howard Wang <howard_wang@realsil.com.cn>
> ---
That is much to short a message for a critical fix.
How about this (AI generated) message. Can I add that during merge?
Subject: [PATCH v2 01/12] net/r8169: fix crash in RTL8168FP init
The rtl8168fp_ops structure was missing the hw_phy_mcu_config function pointer, causing a NULL pointer dereference during device initialization when the driver attempts to configure the PHY microcontroller.
Add hw_phy_mcu_config_8168fp() as a no-op function since the RTL8168FP does not require PHY MCU configuration. This matches the pattern used by other chip variants that don't need PHY MCU updates.
Fixes: d9ee71b5f1bc ("net/r8169: support RTL8168 series")
next prev parent reply other threads:[~2026-02-12 5:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 5:54 [PATCH v2 00/12] net/r8169: update driver with new HW support and fixes Howard Wang
2026-02-10 5:55 ` [PATCH v2 01/12] net/r8169: fix NULL pointer dereference in rtl8168fp_ops Howard Wang
2026-02-11 21:42 ` Stephen Hemminger
2026-02-12 5:51 ` 王颢 [this message]
2026-02-10 5:55 ` [PATCH v2 02/12] net/r8169: tune RX desc fetch num for 8126 and 8127 Howard Wang
2026-02-11 21:43 ` Stephen Hemminger
2026-02-12 5:45 ` 回复: " 王颢
2026-02-10 5:55 ` [PATCH v2 03/12] net/r8169: add support for RTL8168KD Howard Wang
2026-02-10 5:55 ` [PATCH v2 04/12] net/r8169: update hardware configurations for 8127 Howard Wang
2026-02-10 5:55 ` [PATCH v2 05/12] net/r8169: adjust jumbo frame size limit for non-1G cards Howard Wang
2026-02-10 5:55 ` [PATCH v2 06/12] net/r8169: remove support for CFG_METHOD_69 Howard Wang
2026-02-10 5:55 ` [PATCH v2 07/12] net/r8169: update hardware configurations for 8126 Howard Wang
2026-02-10 5:55 ` [PATCH v2 08/12] net/r8169: update hardware configurations for 8125 Howard Wang
2026-02-10 5:55 ` [PATCH v2 09/12] net/r8169: add support for RTL9151 Howard Wang
2026-02-10 5:55 ` [PATCH v2 10/12] net/r8169: add support for RTL8125K Howard Wang
2026-02-10 5:55 ` [PATCH v2 11/12] net/r8169: fix one bug about RTL8168KB Howard Wang
2026-02-10 5:55 ` [PATCH v2 12/12] net/r8169: ensure the old mapping is used Howard Wang
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=a422d66b5d284415a399bbe8ca5f2b7c@realsil.com.cn \
--to=howard_wang@realsil.com.cn \
--cc=dev@dpdk.org \
--cc=pro_nic_dpdk@realtek.com \
--cc=stephen@networkplumber.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