From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Cthomas=2Eweissschuh=40linutronix=2Ede=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: dwmw2@infradead.org, richardcochran@gmail.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mateusz.polchlopek@intel.com,
dwmw@amazon.co.uk, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v2 0/5] ptp: vmclock: bugfixes and cleanups for error handling
Date: Tue, 11 Feb 2025 09:40:32 +0000 [thread overview]
Message-ID: <173926683207.4011842.17472551825427009472.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250207-vmclock-probe-v2-0-bc2fce0bdf07@linutronix.de>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 07 Feb 2025 10:39:01 +0100 you wrote:
> Some error handling issues I noticed while looking at the code.
>
> Only compile-tested.
>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
> Changes in v2:
> - Fix typo in commit message: vmclock_ptp_register()
> - Retarget against net tree
> - Include patch from David. It's at the start of the series so that all
> bugfixes are at the beginning and the logical ordering of my patches
> is not disrupted.
> - Pick up tags from LKML
> - Link to v1: https://lore.kernel.org/r/20250206-vmclock-probe-v1-0-17a3ea07be34@linutronix.de
>
> [...]
Here is the summary with links:
- [net,v2,1/5] ptp: vmclock: Add .owner to vmclock_miscdev_fops
https://git.kernel.org/netdev/net/c/7b07b040257c
- [net,v2,2/5] ptp: vmclock: Set driver data before its usage
https://git.kernel.org/netdev/net/c/f7d07cd4f77d
- [net,v2,3/5] ptp: vmclock: Don't unregister misc device if it was not registered
https://git.kernel.org/netdev/net/c/39e926c3a21b
- [net,v2,4/5] ptp: vmclock: Clean up miscdev and ptp clock through devres
https://git.kernel.org/netdev/net/c/9a884c3800b2
- [net,v2,5/5] ptp: vmclock: Remove goto-based cleanup logic
https://git.kernel.org/netdev/net/c/b4c1fde5ced9
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-02-11 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 9:39 [PATCH net v2 0/5] ptp: vmclock: bugfixes and cleanups for error handling Thomas Weißschuh
2025-02-07 9:39 ` [PATCH net v2 1/5] ptp: vmclock: Add .owner to vmclock_miscdev_fops Thomas Weißschuh
2025-02-07 9:39 ` [PATCH net v2 2/5] ptp: vmclock: Set driver data before its usage Thomas Weißschuh
2025-02-07 9:39 ` [PATCH net v2 3/5] ptp: vmclock: Don't unregister misc device if it was not registered Thomas Weißschuh
2025-02-07 9:39 ` [PATCH net v2 4/5] ptp: vmclock: Clean up miscdev and ptp clock through devres Thomas Weißschuh
2025-02-07 9:39 ` [PATCH net v2 5/5] ptp: vmclock: Remove goto-based cleanup logic Thomas Weißschuh
2025-02-11 9:40 ` 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=173926683207.4011842.17472551825427009472.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Cthomas=2Eweissschuh=40linutronix=2Ede=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=dwmw@amazon.co.uk \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mateusz.polchlopek@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=stable@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