From: Rahul Rameshbabu via ltp <ltp@lists.linux.it>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Linux Kernel Functional Testing <lkft@linaro.org>,
netdev@vger.kernel.org,
Richard Cochran <richardcochran@gmail.com>,
lkft-triage@lists.linaro.org,
"David S. Miller" <davem@davemloft.net>,
Nathan Chancellor <nathan@kernel.org>,
Saeed Mahameed <saeed@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Gal Pressman <gal@nvidia.com>, LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH net v1] ptp: Make max_phase_adjustment sysfs device attribute invisible when not supported
Date: Tue, 27 Jun 2023 19:22:38 -0700 [thread overview]
Message-ID: <87ilb8ba1d.fsf@nvidia.com> (raw)
In-Reply-To: <7fa02bc1-64bd-483d-b3e9-f4ffe0bbb9fb@lunn.ch> (Andrew Lunn's message of "Wed, 28 Jun 2023 03:16:43 +0200")
On Wed, 28 Jun, 2023 03:16:43 +0200 Andrew Lunn <andrew@lunn.ch> wrote:
> On Tue, Jun 27, 2023 at 04:21:39PM -0700, Rahul Rameshbabu 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/
>
> I think Signed-off-by should be last.
I can agree with this. Follows the "real route" of the patch, reports
came in and then the patch was implemented and signed-off.
>
>> diff --git a/drivers/ptp/ptp_sysfs.c b/drivers/ptp/ptp_sysfs.c
>> index 77219cdcd683..6e4d5456a885 100644
>> --- a/drivers/ptp/ptp_sysfs.c
>> +++ b/drivers/ptp/ptp_sysfs.c
>> @@ -358,6 +358,9 @@ static umode_t ptp_is_attribute_visible(struct kobject *kobj,
>> attr == &dev_attr_max_vclocks.attr) {
>> if (ptp->is_virtual_clock)
>> mode = 0;
>> + } else if (attr == &dev_attr_max_phase_adjustment.attr) {
>> + if (!info->adjphase || !info->getmaxphase)
>> + mode = 0;
>
> Maybe it is time to turn this into a switch statement?
I agree. However, I do not want to conflate two separate things being a
bugfix and a cleanup. I think we can do one of two options.
1. We can take this patch as is, but I submit a subsequent cleanup patch for
this.
2. I can turn this into a two patch submission where the first patch
does the conversion.
I am a fan of the first option personally.
>
> I also wounder if this really is something for net. How do you think
> this patch matches against the stable rules?
Apologize in advance but not sure I am following along. The commit for
the patch the introduces the problematic logic has made its way to net
and this patch is a fix. Therefore, isn't net the right tree to target?
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=c3b60ab7a4dff6e6e608e685b70ddc3d6b2aca81
>
> Andrew
Thanks,
Rahul Rameshbabu
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org,
Richard Cochran <richardcochran@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
Saeed Mahameed <saeed@kernel.org>, Gal Pressman <gal@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
lkft-triage@lists.linaro.org, LTP List <ltp@lists.linux.it>,
Nathan Chancellor <nathan@kernel.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux Kernel Functional Testing <lkft@linaro.org>
Subject: Re: [PATCH net v1] ptp: Make max_phase_adjustment sysfs device attribute invisible when not supported
Date: Tue, 27 Jun 2023 19:22:38 -0700 [thread overview]
Message-ID: <87ilb8ba1d.fsf@nvidia.com> (raw)
In-Reply-To: <7fa02bc1-64bd-483d-b3e9-f4ffe0bbb9fb@lunn.ch> (Andrew Lunn's message of "Wed, 28 Jun 2023 03:16:43 +0200")
On Wed, 28 Jun, 2023 03:16:43 +0200 Andrew Lunn <andrew@lunn.ch> wrote:
> On Tue, Jun 27, 2023 at 04:21:39PM -0700, Rahul Rameshbabu 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/
>
> I think Signed-off-by should be last.
I can agree with this. Follows the "real route" of the patch, reports
came in and then the patch was implemented and signed-off.
>
>> diff --git a/drivers/ptp/ptp_sysfs.c b/drivers/ptp/ptp_sysfs.c
>> index 77219cdcd683..6e4d5456a885 100644
>> --- a/drivers/ptp/ptp_sysfs.c
>> +++ b/drivers/ptp/ptp_sysfs.c
>> @@ -358,6 +358,9 @@ static umode_t ptp_is_attribute_visible(struct kobject *kobj,
>> attr == &dev_attr_max_vclocks.attr) {
>> if (ptp->is_virtual_clock)
>> mode = 0;
>> + } else if (attr == &dev_attr_max_phase_adjustment.attr) {
>> + if (!info->adjphase || !info->getmaxphase)
>> + mode = 0;
>
> Maybe it is time to turn this into a switch statement?
I agree. However, I do not want to conflate two separate things being a
bugfix and a cleanup. I think we can do one of two options.
1. We can take this patch as is, but I submit a subsequent cleanup patch for
this.
2. I can turn this into a two patch submission where the first patch
does the conversion.
I am a fan of the first option personally.
>
> I also wounder if this really is something for net. How do you think
> this patch matches against the stable rules?
Apologize in advance but not sure I am following along. The commit for
the patch the introduces the problematic logic has made its way to net
and this patch is a fix. Therefore, isn't net the right tree to target?
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=c3b60ab7a4dff6e6e608e685b70ddc3d6b2aca81
>
> Andrew
Thanks,
Rahul Rameshbabu
next prev parent reply other threads:[~2023-06-29 9:06 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 ` Rahul Rameshbabu via ltp [this message]
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
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=87ilb8ba1d.fsf@nvidia.com \
--to=ltp@lists.linux.it \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lkft@linaro.org \
--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.