From: patchwork-bot+netdevbpf@kernel.org
To: Buday Csaba <buday.csaba@prolan.hu>
Cc: wei.fang@nxp.com, frank.li@nxp.com, shenwei.wang@nxp.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
francesco.dolcini@toradex.com, bence98@sch.bme.hu,
imx@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 1/1] net: fec: fix the PTP periodic output sysfs interface
Date: Fri, 27 Mar 2026 03:20:06 +0000 [thread overview]
Message-ID: <177458160604.3283168.10059556551058678731.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <8ec2afe88423c2231f9cf8044d212ce57846670e.1774359059.git.buday.csaba@prolan.hu>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 24 Mar 2026 14:32:30 +0100 you wrote:
> When the PPS channel configuration was implemented, the channel
> index for the periodic outputs was configured as the hardware
> channel number.
>
> The sysfs interface uses a logical channel index, and rejects numbers
> greater than `n_per_out` (see period_store() in ptp_sysfs.c).
> That property was left at 1, since the driver implements channel
> selection, not simultaneous operation of multiple PTP hardware timer
> channels.
>
> [...]
Here is the summary with links:
- [net,v3,1/1] net: fec: fix the PTP periodic output sysfs interface
https://git.kernel.org/netdev/net/c/e8e44c98f789
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-03-27 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 13:32 [PATCH net v3 1/1] net: fec: fix the PTP periodic output sysfs interface Buday Csaba
2026-03-27 3:20 ` 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=177458160604.3283168.10059556551058678731.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bence98@sch.bme.hu \
--cc=buday.csaba@prolan.hu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=francesco.dolcini@toradex.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@nxp.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