From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
andrew+netdev@lunn.ch, netdev@vger.kernel.org,
Milena Olech <milena.olech@intel.com>,
przemyslaw.kitszel@intel.com, karol.kolacinski@intel.com,
richardcochran@gmail.com,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Willem de Bruijn <willemb@google.com>,
Mina Almasry <almasrymina@google.com>,
Samuel Salin <Samuel.salin@intel.com>
Subject: Re: [PATCH net-next 01/10] idpf: add initial PTP support
Date: Tue, 25 Mar 2025 05:44:21 -0700 [thread overview]
Message-ID: <20250325054421.7e60e5ad@kernel.org> (raw)
In-Reply-To: <20250318161327.2532891-2-anthony.l.nguyen@intel.com>
On Tue, 18 Mar 2025 09:13:16 -0700 Tony Nguyen wrote:
> From: Milena Olech <milena.olech@intel.com>
>
> PTP feature is supported if the VIRTCHNL2_CAP_PTP is negotiated during the
> capabilities recognition. Initial PTP support includes PTP initialization
> and registration of the clock.
>
> Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>
> Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
> Reviewed-by: Willem de Bruijn <willemb@google.com>
> Tested-by: Mina Almasry <almasrymina@google.com>
> Signed-off-by: Milena Olech <milena.olech@intel.com>
> Tested-by: Samuel Salin <Samuel.salin@intel.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Would be great to see a review tag from Jake on these :(
> +#if IS_ENABLED(CONFIG_PTP_1588_CLOCK)
> +int idpf_ptp_init(struct idpf_adapter *adapter);
> +void idpf_ptp_release(struct idpf_adapter *adapter);
> +#else /* CONFIG_PTP_1588_CLOCK */
> +static inline int idpf_ptp_init(struct idpf_adapter *adapter)
> +{
> + return 0;
> +}
> +
> +static inline void idpf_ptp_release(struct idpf_adapter *adapter) { }
> +#endif /* CONFIG_PTP_1588_CLOCK */
> +#endif /* _IDPF_PTP_H */
You add an unusual number of ifdefs for CONFIG_PTP_1588_CLOCK.
Is this really necessary? What breaks if 1588 is not enabled?
next prev parent reply other threads:[~2025-03-25 12:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 16:13 [PATCH net-next 00/10][pull request] idpf: add initial PTP support Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 01/10] " Tony Nguyen
2025-03-25 12:44 ` Jakub Kicinski [this message]
2025-03-25 21:05 ` Jacob Keller
2025-04-02 13:16 ` Olech, Milena
2025-03-18 16:13 ` [PATCH net-next 02/10] virtchnl: add PTP virtchnl definitions Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 03/10] idpf: move virtchnl structures to the header file Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 04/10] idpf: negotiate PTP capabilities and get PTP clock Tony Nguyen
2025-03-25 12:49 ` Jakub Kicinski
2025-03-25 21:07 ` Jacob Keller
2025-03-26 8:24 ` Przemek Kitszel
2025-04-02 15:23 ` Olech, Milena
2025-04-02 16:37 ` Jakub Kicinski
2025-03-18 16:13 ` [PATCH net-next 05/10] idpf: add mailbox access to read PTP clock time Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 06/10] idpf: add PTP clock configuration Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 07/10] idpf: add Tx timestamp capabilities negotiation Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 08/10] idpf: add Tx timestamp flows Tony Nguyen
2025-03-25 13:00 ` Jakub Kicinski
2025-03-25 21:10 ` Jacob Keller
2025-04-02 14:57 ` Olech, Milena
2025-03-18 16:13 ` [PATCH net-next 09/10] idpf: add support for Rx timestamping Tony Nguyen
2025-03-18 16:13 ` [PATCH net-next 10/10] idpf: change the method for mailbox workqueue allocation Tony Nguyen
2025-03-25 21:08 ` Jacob Keller
2025-04-02 13:22 ` Olech, Milena
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=20250325054421.7e60e5ad@kernel.org \
--to=kuba@kernel.org \
--cc=Samuel.salin@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=karol.kolacinski@intel.com \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
--cc=willemb@google.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 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.