From: patchwork-bot+netdevbpf@kernel.org
To: Wojtek Wasko <wwasko@nvidia.com>
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
vadim.fedorenko@linux.dev, kuba@kernel.org, horms@kernel.org,
anna-maria@linutronix.de, frederic@kernel.org, pabeni@redhat.com,
tglx@linutronix.de
Subject: Re: [PATCH net-next v4 0/3] Permission checks for dynamic POSIX clocks
Date: Wed, 05 Mar 2025 12:50:33 +0000 [thread overview]
Message-ID: <174117903325.870005.17317001813536727921.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250303161345.3053496-1-wwasko@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 3 Mar 2025 18:13:42 +0200 you wrote:
> Dynamic clocks - such as PTP clocks - extend beyond the standard POSIX
> clock API by using ioctl calls. While file permissions are enforced for
> standard POSIX operations, they are not implemented for ioctl calls,
> since the POSIX layer cannot differentiate between calls which modify
> the clock's state (like enabling PPS output generation) and those that
> don't (such as retrieving the clock's PPS capabilities).
>
> [...]
Here is the summary with links:
- [net-next,v4,1/3] posix-clock: Store file pointer in struct posix_clock_context
https://git.kernel.org/netdev/net-next/c/e859d375d169
- [net-next,v4,2/3] ptp: Add PHC file mode checks. Allow RO adjtime() without FMODE_WRITE.
https://git.kernel.org/netdev/net-next/c/b4e53b15c04e
- [net-next,v4,3/3] testptp: Add option to open PHC in readonly mode
https://git.kernel.org/netdev/net-next/c/76868642e427
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-03-05 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 16:13 [PATCH net-next v4 0/3] Permission checks for dynamic POSIX clocks Wojtek Wasko
2025-03-03 16:13 ` [PATCH net-next v4 1/3] posix-clock: Store file pointer in struct posix_clock_context Wojtek Wasko
2025-03-03 16:13 ` [PATCH net-next v4 2/3] ptp: Add PHC file mode checks. Allow RO adjtime() without FMODE_WRITE Wojtek Wasko
2025-03-03 19:33 ` Thomas Gleixner
2025-03-03 16:13 ` [PATCH net-next v4 3/3] testptp: Add option to open PHC in readonly mode Wojtek Wasko
2025-03-05 12:50 ` 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=174117903325.870005.17317001813536727921.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--cc=vadim.fedorenko@linux.dev \
--cc=wwasko@nvidia.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;
as well as URLs for NNTP newsgroup(s).