From: patchwork-bot+netdevbpf@kernel.org
To: Rahul Rameshbabu <rrameshbabu@nvidia.com>
Cc: lkft@linaro.org, netdev@vger.kernel.org,
richardcochran@gmail.com, lkft-triage@lists.linaro.org,
davem@davemloft.net, nathan@kernel.org, saeed@kernel.org,
kuba@kernel.org, pabeni@redhat.com, gal@nvidia.com,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH net v1] ptp: Make max_phase_adjustment sysfs device attribute invisible when not supported
Date: Mon, 03 Jul 2023 20:40:21 +0000 [thread overview]
Message-ID: <168841682144.15554.860228703846635745.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230627232139.213130-1-rrameshbabu@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Jun 2023 16:21:39 -0700 you wrote:
> The .adjphase operation is an operation that is implemented only by certain
> PHCs. The sysfs device attribute node for querying the maximum phase
> adjustment supported should not be exposed on devices that do not support
> .adjphase.
>
> Fixes: c3b60ab7a4df ("ptp: Add .getmaxphase callback to ptp_clock_info")
> Signed-off-by: Rahul Rameshbabu <rrameshbabu@nvidia.com>
> Reported-by: Nathan Chancellor <nathan@kernel.org>
> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> Link: https://lore.kernel.org/netdev/20230627162146.GA114473@dev-arch.thelio-3990X/
> Link: https://lore.kernel.org/all/CA+G9fYtKCZeAUTtwe69iK8Xcz1mOKQzwcy49wd+imZrfj6ifXA@mail.gmail.com/
>
> [...]
Here is the summary with links:
- [net,v1] ptp: Make max_phase_adjustment sysfs device attribute invisible when not supported
https://git.kernel.org/netdev/net/c/2c5d234d7f55
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Rahul Rameshbabu <rrameshbabu@nvidia.com>
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
pabeni@redhat.com, kuba@kernel.org, saeed@kernel.org,
gal@nvidia.com, davem@davemloft.net,
lkft-triage@lists.linaro.org, ltp@lists.linux.it,
nathan@kernel.org, naresh.kamboju@linaro.org, lkft@linaro.org
Subject: Re: [PATCH net v1] ptp: Make max_phase_adjustment sysfs device attribute invisible when not supported
Date: Mon, 03 Jul 2023 20:40:21 +0000 [thread overview]
Message-ID: <168841682144.15554.860228703846635745.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230627232139.213130-1-rrameshbabu@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Jun 2023 16:21:39 -0700 you wrote:
> The .adjphase operation is an operation that is implemented only by certain
> PHCs. The sysfs device attribute node for querying the maximum phase
> adjustment supported should not be exposed on devices that do not support
> .adjphase.
>
> Fixes: c3b60ab7a4df ("ptp: Add .getmaxphase callback to ptp_clock_info")
> Signed-off-by: Rahul Rameshbabu <rrameshbabu@nvidia.com>
> Reported-by: Nathan Chancellor <nathan@kernel.org>
> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> Link: https://lore.kernel.org/netdev/20230627162146.GA114473@dev-arch.thelio-3990X/
> Link: https://lore.kernel.org/all/CA+G9fYtKCZeAUTtwe69iK8Xcz1mOKQzwcy49wd+imZrfj6ifXA@mail.gmail.com/
>
> [...]
Here is the summary with links:
- [net,v1] ptp: Make max_phase_adjustment sysfs device attribute invisible when not supported
https://git.kernel.org/netdev/net/c/2c5d234d7f55
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-07-11 11:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 23:21 [LTP] [PATCH net v1] ptp: Make max_phase_adjustment sysfs device attribute invisible when not supported Rahul Rameshbabu via ltp
2023-06-27 23:21 ` Rahul Rameshbabu
2023-06-27 23:33 ` [LTP] " Nathan Chancellor
2023-06-27 23:33 ` Nathan Chancellor
2023-06-28 1:16 ` [LTP] " Andrew Lunn
2023-06-28 1:16 ` Andrew Lunn
2023-06-28 2:22 ` [LTP] " Rahul Rameshbabu via ltp
2023-06-28 2:22 ` Rahul Rameshbabu
2023-06-28 14:35 ` [LTP] " Andrew Lunn
2023-06-28 17:48 ` Rahul Rameshbabu via ltp
2023-06-28 18:15 ` Andrew Lunn
2023-06-28 20:38 ` Jakub Kicinski
2023-06-28 20:38 ` Jakub Kicinski
2023-06-28 20:46 ` [LTP] " Andrew Lunn
2023-06-28 20:46 ` Andrew Lunn
2023-06-28 20:55 ` [LTP] " Rahul Rameshbabu via ltp
2023-06-29 18:06 ` Jakub Kicinski
2023-06-29 18:06 ` Jakub Kicinski
2023-06-30 3:33 ` [LTP] " Richard Cochran
2023-06-30 3:33 ` Richard Cochran
2023-06-30 3:32 ` [LTP] " Richard Cochran
2023-06-30 3:32 ` Richard Cochran
2023-07-03 5:10 ` [LTP] " Petr Vorel
2023-07-03 5:10 ` Petr Vorel
2023-07-03 12:53 ` Cyril Hrubis
2023-07-03 12:53 ` Cyril Hrubis
2023-07-03 20:40 ` patchwork-bot+netdevbpf [this message]
2023-07-03 20:40 ` patchwork-bot+netdevbpf
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=168841682144.15554.860228703846635745.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lkft@linaro.org \
--cc=ltp@lists.linux.it \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeed@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 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.