From: patchwork-bot+netdevbpf@kernel.org
To: Bui Duc Phuc <phucduc.bui@gmail.com>
Cc: wei.fang@nxp.com, frank.li@nxp.com, shenwei.wang@nxp.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
imx@lists.linux.dev, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v6 1/2] net: fec: Propagate PTP initialization errors
Date: Tue, 15 Sep 2026 08:20:13 +0000 [thread overview]
Message-ID: <178946041395.1433766.9518357257056038239.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260911040021.12289-1-phucduc.bui@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 11 Sep 2026 11:00:20 +0700 you wrote:
> From: bui duc phuc <phucduc.bui@gmail.com>
>
> Change fec_ptp_init() to return an error code instead of silently
> ignoring failures during PTP initialization.
>
> The PPS IRQ is not required for the FEC/PTP functionality, so its
> absence should not make the probe fail. However, an unavailable
> optional IRQ should be distinguished from an actual error returned
> during the IRQ lookup.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/2] net: fec: Propagate PTP initialization errors
https://git.kernel.org/netdev/net-next/c/2343cff0b382
- [net-next,v6,2/2] net: fec: Handle optional IRQ lookup errors correctly
https://git.kernel.org/netdev/net-next/c/20d1b74a32d0
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:[~2026-09-15 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 4:00 [PATCH net-next v6 1/2] net: fec: Propagate PTP initialization errors phucduc.bui
2026-09-11 4:00 ` [PATCH net-next v6 2/2] net: fec: Handle optional IRQ lookup errors correctly phucduc.bui
2026-09-12 4:03 ` sashiko-bot
2026-09-12 4:03 ` [PATCH net-next v6 1/2] net: fec: Propagate PTP initialization errors sashiko-bot
2026-09-15 8:20 ` 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=178946041395.1433766.9518357257056038239.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frank.li@nxp.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=phucduc.bui@gmail.com \
--cc=richardcochran@gmail.com \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@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 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.