From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: "intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Drewek, Wojciech" <wojciech.drewek@intel.com>,
Rahul Rameshbabu <rrameshbabu@nvidia.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v6 11/12] iavf: handle SIOCSHWTSTAMP and SIOCGHWTSTAMP
Date: Wed, 29 May 2024 15:12:09 +0200 [thread overview]
Message-ID: <18d08ef2-d08b-425f-84f8-a5281de978fb@intel.com> (raw)
In-Reply-To: <CO1PR11MB508916EC8EF80A8EFE6EF19DD6F12@CO1PR11MB5089.namprd11.prod.outlook.com>
On 5/29/2024 1:54 AM, Keller, Jacob E wrote:
>
>
>> -----Original Message-----
>> From: Jakub Kicinski <kuba@kernel.org>
>> Sent: Tuesday, May 28, 2024 1:01 PM
>> To: Polchlopek, Mateusz <mateusz.polchlopek@intel.com>
>> Cc: intel-wired-lan@lists.osuosl.org; netdev@vger.kernel.org; Keller, Jacob E
>> <jacob.e.keller@intel.com>; Drewek, Wojciech <wojciech.drewek@intel.com>;
>> Rahul Rameshbabu <rrameshbabu@nvidia.com>
>> Subject: Re: [Intel-wired-lan] [PATCH iwl-next v6 11/12] iavf: handle
>> SIOCSHWTSTAMP and SIOCGHWTSTAMP
>>
>> On Tue, 28 May 2024 07:23:00 -0400 Mateusz Polchlopek wrote:
>>> + .ndo_eth_ioctl = iavf_do_ioctl,
>>
>> Please use the new ndos:
>>
>> * int (*ndo_hwtstamp_get)(struct net_device *dev,
>> * struct kernel_hwtstamp_config *kernel_config);
>> * Get the currently configured hardware timestamping parameters for the
>> * NIC device.
>> *
>> * int (*ndo_hwtstamp_set)(struct net_device *dev,
>> * struct kernel_hwtstamp_config *kernel_config,
>> * struct netlink_ext_ack *extack);
>> * Change the hardware timestamping parameters for NIC device.
>
> +1, this is an excellent cleanup.
>
> Thanks,
> Jake
Hmmm... sounds good :) Thanks for pointing that, I will take a look
and will try to prepare solution in next version
next prev parent reply other threads:[~2024-05-29 13:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 11:22 [Intel-wired-lan] [PATCH iwl-next v6 00/12] Add support for Rx timestamping for both ice and iavf drivers Mateusz Polchlopek
2024-05-28 11:22 ` [Intel-wired-lan] [PATCH iwl-next v6 01/12] virtchnl: add support for enabling PTP on iAVF Mateusz Polchlopek
2024-05-28 11:22 ` [Intel-wired-lan] [PATCH iwl-next v6 02/12] ice: support Rx timestamp on flex descriptor Mateusz Polchlopek
2024-05-28 11:22 ` [Intel-wired-lan] [PATCH iwl-next v6 03/12] virtchnl: add enumeration for the rxdid format Mateusz Polchlopek
2024-05-28 11:22 ` [Intel-wired-lan] [PATCH iwl-next v6 04/12] iavf: add support for negotiating flexible RXDID format Mateusz Polchlopek
2024-05-28 11:22 ` [Intel-wired-lan] [PATCH iwl-next v6 05/12] iavf: negotiate PTP capabilities Mateusz Polchlopek
2024-05-28 11:22 ` [Intel-wired-lan] [PATCH iwl-next v6 06/12] iavf: add initial framework for registering PTP clock Mateusz Polchlopek
2024-05-28 11:22 ` [Intel-wired-lan] [PATCH iwl-next v6 07/12] iavf: add support for indirect access to PHC time Mateusz Polchlopek
2024-05-28 11:22 ` [Intel-wired-lan] [PATCH iwl-next v6 08/12] iavf: periodically cache " Mateusz Polchlopek
2024-05-28 11:22 ` [Intel-wired-lan] [PATCH iwl-next v6 09/12] iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors Mateusz Polchlopek
2024-05-28 11:22 ` [Intel-wired-lan] [PATCH iwl-next v6 10/12] iavf: Implement checking DD desc field Mateusz Polchlopek
2024-05-28 11:23 ` [Intel-wired-lan] [PATCH iwl-next v6 11/12] iavf: handle SIOCSHWTSTAMP and SIOCGHWTSTAMP Mateusz Polchlopek
2024-05-28 20:00 ` Jakub Kicinski
2024-05-28 23:54 ` Keller, Jacob E
2024-05-29 13:12 ` Mateusz Polchlopek [this message]
2024-05-28 11:23 ` [Intel-wired-lan] [PATCH iwl-next v6 12/12] iavf: add support for Rx timestamps to hotpath Mateusz Polchlopek
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=18d08ef2-d08b-425f-84f8-a5281de978fb@intel.com \
--to=mateusz.polchlopek@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rrameshbabu@nvidia.com \
--cc=wojciech.drewek@intel.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;
as well as URLs for NNTP newsgroup(s).