diff options
| author | Jakub Kicinski <[email protected]> | 2025-09-22 18:36:32 +0000 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2025-09-22 18:36:33 +0000 |
| commit | 207b45e8533f9a5b3206b6a85a984464e646b0e1 (patch) | |
| tree | a28142a577e08b4cf3697bc453bf6ffb40bb72d1 /lib/xarray.c | |
| parent | ethernet: rvu-af: Remove slash from the driver name (diff) | |
| parent | ptp: document behavior of PTP_STRICT_FLAGS (diff) | |
| download | kernel-207b45e8533f9a5b3206b6a85a984464e646b0e1.tar.gz kernel-207b45e8533f9a5b3206b6a85a984464e646b0e1.zip | |
Merge branch 'broadcom-report-the-supported-flags-for-ancillary-features'
Jacob Keller says:
====================
broadcom: report the supported flags for ancillary features
James Clark reported off list that the broadcom PHY PTP driver was
incorrectly handling PTP_EXTTS_REQUEST and PTP_PEROUT_REQUEST ioctls since
the conversion to the .supported_*_flags fields. This series fixes the
driver to correctly report its flags through the .supported_perout_flags
and .supported_extts_flags fields. It also contains an update to comment
the behavior of the PTP_STRICT_FLAGS being always enabled for
PTP_EXTTS_REQUEST2.
I plan to follow up this series with some improvements to the PTP
documentation better explaining each flag and the expectation of the driver
APIs.
====================
Link: https://patch.msgid.link/20250918-jk-fix-bcm-phy-supported-flags-v1-0-747b60407c9c@intel.com
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'lib/xarray.c')
0 files changed, 0 insertions, 0 deletions