From: patchwork-bot+netdevbpf@kernel.org
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
kernel.hbk@gmail.com, paul.barker.ct@bp.renesas.com,
niklas.soderlund@ragnatech.se, bryan.whitehead@microchip.com,
UNGLinuxDriver@microchip.com, florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk,
jonathan.lemon@gmail.com, l@ssejohnsen.me,
vadim.fedorenko@linux.dev, michal.swiatkowski@linux.intel.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net v2 0/5] net: ptp: fix egregious supported flag checks
Date: Thu, 20 Mar 2025 08:20:35 +0000 [thread overview]
Message-ID: <174245883577.1343567.2281095132838177451.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250312-jk-net-fixes-supported-extts-flags-v2-0-ea930ba82459@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 12 Mar 2025 15:15:49 -0700 you wrote:
> In preparation for adding .supported_extts_flags and
> .supported_perout_flags to the ptp_clock_info structure, fix a couple of
> places where drivers get existing flag gets grossly incorrect.
>
> The igb driver claims 82580 supports strictly validating PTP_RISING_EDGE
> and PTP_FALLING_EDGE, but doesn't actually check the flags. Fix the driver
> to require that the request match both edges, as this is implied by the
> datasheet description.
>
> [...]
Here is the summary with links:
- [net,v2,1/5] igb: reject invalid external timestamp requests for 82580-based HW
https://git.kernel.org/netdev/net-next/c/5eada2aabf13
- [net,v2,2/5] renesas: reject PTP_STRICT_FLAGS as unsupported
https://git.kernel.org/netdev/net-next/c/51d58c0c7921
- [net,v2,3/5] net: lan743x: reject unsupported external timestamp requests
https://git.kernel.org/netdev/net-next/c/c0b4ddd30871
- [net,v2,4/5] broadcom: fix supported flag check in periodic output function
https://git.kernel.org/netdev/net-next/c/af2b428f7992
- [net,v2,5/5] ptp: ocp: reject unsupported periodic output flags
https://git.kernel.org/netdev/net-next/c/8dcfc910a81d
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-20 8:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 22:15 [PATCH net v2 0/5] net: ptp: fix egregious supported flag checks Jacob Keller
2025-03-12 22:15 ` [PATCH net v2 1/5] igb: reject invalid external timestamp requests for 82580-based HW Jacob Keller
2025-03-18 14:06 ` Simon Horman
2025-03-12 22:15 ` [PATCH net v2 2/5] renesas: reject PTP_STRICT_FLAGS as unsupported Jacob Keller
2025-03-13 9:45 ` Niklas Söderlund
2025-03-18 14:07 ` Simon Horman
2025-03-12 22:15 ` [PATCH net v2 3/5] net: lan743x: reject unsupported external timestamp requests Jacob Keller
2025-03-18 14:08 ` Simon Horman
2025-03-12 22:15 ` [PATCH net v2 4/5] broadcom: fix supported flag check in periodic output function Jacob Keller
2025-03-18 14:09 ` Simon Horman
2025-03-12 22:15 ` [PATCH net v2 5/5] ptp: ocp: reject unsupported periodic output flags Jacob Keller
2025-03-18 14:10 ` Simon Horman
2025-03-19 21:21 ` [PATCH net v2 0/5] net: ptp: fix egregious supported flag checks Paolo Abeni
2025-03-19 23:56 ` Jacob Keller
2025-03-20 8: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=174245883577.1343567.2281095132838177451.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jonathan.lemon@gmail.com \
--cc=kernel.hbk@gmail.com \
--cc=kuba@kernel.org \
--cc=l@ssejohnsen.me \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=pabeni@redhat.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
/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).