From: Jakub Kicinski <kuba@kernel.org>
To: Xiangwu Lai <laixiangwu@cmss.chinamobile.com>
Cc: netdev-bot+sinfo@kernel.org, netdev@vger.kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
pabeni@redhat.com, danishanwar@ti.com, rogerq@kernel.org,
jan.kiszka@siemens.com, diogo.ivo@siemens.com,
haokexin@gmail.com, horms@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net 0/4] net: ti: icssg: Fix device_node handling in prueth_probe()
Date: Thu, 12 Nov 2026 09:37:06 -0800 [thread overview]
Message-ID: <20261112093706.55e00f17@kernel.org> (raw)
In-Reply-To: <20261110150500.3142-laixiangwu@cmss.chinamobile.com>
On Tue, 10 Nov 2026 15:31:38 +0800 Xiangwu Lai wrote:
> The same information was provided for the v1 postings of
> patches 1 and 2 here:
If only you read the message the bot sent you would would know that
you're supposed to add this to the cover letter when respinning.
next prev parent reply other threads:[~2026-11-12 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 6:41 [PATCH v2 net 0/4] net: ti: icssg: Fix device_node handling in prueth_probe() Xiangwu Lai
2026-11-10 6:41 ` [PATCH v2 net 1/4] net: ti: icssg-prueth: Fix device_node refcount leak " Xiangwu Lai
2026-11-10 6:41 ` [PATCH v2 net 2/4] net: ti: icssg-prueth-sr1: " Xiangwu Lai
2026-11-10 6:41 ` [PATCH v2 net 3/4] net: ti: icssg-prueth: Fix port scan issues " Xiangwu Lai
2026-11-10 6:41 ` [PATCH v2 net 4/4] net: ti: icssg-prueth-sr1: " Xiangwu Lai
2026-11-10 6:46 ` [PATCH v2 net 0/4] net: ti: icssg: Fix device_node handling " netdev-bot+sinfo
2026-11-10 7:31 ` Xiangwu Lai
2026-11-12 17:37 ` Jakub Kicinski [this message]
2026-11-11 10:32 ` Xiangwu Lai
2026-11-12 17:40 ` patchwork-bot+netdevbpf
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=20261112093706.55e00f17@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@kernel.org \
--cc=haokexin@gmail.com \
--cc=horms@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=laixiangwu@cmss.chinamobile.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@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