From: patchwork-bot+netdevbpf@kernel.org
To: Wei Fang <wei.fang@nxp.com>
Cc: claudiu.manoil@nxp.com, vladimir.oltean@nxp.com,
xiaoning.wang@nxp.com, yangbo.lu@nxp.com,
richardcochran@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, Frank.Li@nxp.com, imx@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] net: enetc: improve the interface for obtaining phc_index
Date: Mon, 22 Sep 2025 19:00:26 +0000 [thread overview]
Message-ID: <175856762699.1122110.3761628175335219202.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250919084509.1846513-1-wei.fang@nxp.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 19 Sep 2025 16:45:07 +0800 you wrote:
> The first patch is to fix the issue that a sleeping function is called
> in the context of rcu_read_lock(). The second patch is to use the generic
> API instead of the custom API to get phc_index. In addition, the second
> patch depends on the first patch to work.
>
> Note, the first patch is a fix, but the issue does not exist in the net
> tree, so the target tree is net-next.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] net: enetc: fix sleeping function called from rcu_read_lock() context
https://git.kernel.org/netdev/net-next/c/26644c90e8fb
- [v2,net-next,2/2] net: enetc: use generic interfaces to get phc_index for ENETC v1
https://git.kernel.org/netdev/net-next/c/ac0e650fde45
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-09-22 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 8:45 [PATCH v2 net-next 0/2] net: enetc: improve the interface for obtaining phc_index Wei Fang
2025-09-19 8:45 ` [PATCH v2 net-next 1/2] net: enetc: fix sleeping function called from rcu_read_lock() context Wei Fang
2025-09-19 8:45 ` [PATCH v2 net-next 2/2] net: enetc: use generic interfaces to get phc_index for ENETC v1 Wei Fang
2025-09-22 11:41 ` [PATCH v2 net-next 0/2] net: enetc: improve the interface for obtaining phc_index Vladimir Oltean
2025-09-22 19:00 ` patchwork-bot+netdevbpf [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=175856762699.1122110.3761628175335219202.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.com \
--cc=yangbo.lu@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox