From: patchwork-bot+netdevbpf@kernel.org
To: Sven Schnelle <svens@linux.ibm.com>
Cc: richardcochran@gmail.com, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com
Subject: Re: [PATCH v2 0/2] Add missing facility check to ptp_s390 driver
Date: Thu, 23 Jul 2026 14:10:18 +0000 [thread overview]
Message-ID: <178481581889.2248593.3567702646132973015.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260714130342.1971700-1-svens@linux.ibm.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 14 Jul 2026 15:03:40 +0200 you wrote:
> This patchset adds a missing facility check and a check that the 'query
> physical clock' (PTFF QPT) function is actually available. If it's not
> present, no qpt ptp device will be registered. In order to use ptff_query()
> in a module, the first patch adds a EXPORT_SYMBOL() to export
> ptff_function_mask.
>
> Changes in v2:
> - drop CC check
> - add PTFF QAF check
> - add patch to export ptff_function_mask
>
> [...]
Here is the summary with links:
- [v2,1/2] s390/ptff: Export ptff_function_mask[]
https://git.kernel.org/netdev/net/c/9de445d8296a
- [v2,2/2] ptp: ptp_s390: Add missing facility check
https://git.kernel.org/netdev/net/c/e78f1ac37afc
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-07-23 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 13:03 [PATCH v2 0/2] Add missing facility check to ptp_s390 driver Sven Schnelle
2026-07-14 13:03 ` [PATCH v2 1/2] s390/ptff: Export ptff_function_mask[] Sven Schnelle
2026-07-14 13:36 ` Heiko Carstens
2026-07-14 13:03 ` [PATCH v2 2/2] ptp: ptp_s390: Add missing facility check Sven Schnelle
2026-07-14 13:38 ` Heiko Carstens
2026-07-23 14:10 ` 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=178481581889.2248593.3567702646132973015.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=svens@linux.ibm.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