Netdev List
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Milena Olech <milena.olech@intel.com>,  intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org,  anthony.l.nguyen@intel.com,
	 przemyslaw.kitszel@intel.com,
	 Milena Olech <milena.olech@intel.com>,
	 Alexander Lobakin <aleksander.lobakin@intel.com>,
	 Emil Tantilov <emil.s.tantilov@intel.com>,
	 Pavan Kumar Linga <pavan.kumar.linga@intel.com>
Subject: Re: [PATCH v3 iwl-next 07/10] idpf: add Tx timestamp capabilities negotiation
Date: Thu, 19 Dec 2024 10:05:56 -0500	[thread overview]
Message-ID: <67643654983ec_1d0f5c29421@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20241219094411.110082-8-milena.olech@intel.com>

Milena Olech wrote:
> Tx timestamp capabilities are negotiated for the uplink Vport.
> Driver receives information about the number of available Tx timestamp
> latches, the size of Tx timestamp value and the set of indexes used
> for Tx timestamping.
> 
> Add function to get the Tx timestamp capabilities and parse the uplink
> vport flag.
> 
> Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>
> Co-developed-by: Emil Tantilov <emil.s.tantilov@intel.com>
> Signed-off-by: Emil Tantilov <emil.s.tantilov@intel.com>
> Co-developed-by: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
> Signed-off-by: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
> Signed-off-by: Milena Olech <milena.olech@intel.com>

Reviewed-by: Willem de Bruijn <willemb@google.com>

  reply	other threads:[~2024-12-19 15:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19  9:44 [PATCH v3 iwl-next 00/10] idpf: add initial PTP support Milena Olech
2024-12-19  9:44 ` [PATCH v3 iwl-next 01/10] " Milena Olech
2024-12-19  9:44 ` [PATCH v3 iwl-next 02/10] virtchnl: add PTP virtchnl definitions Milena Olech
2024-12-19  9:44 ` [PATCH v3 iwl-next 03/10] idpf: move virtchnl structures to the header file Milena Olech
2024-12-19  9:44 ` [PATCH v3 iwl-next 04/10] idpf: negotiate PTP capabilities and get PTP clock Milena Olech
2024-12-19  9:44 ` [PATCH v3 iwl-next 05/10] idpf: add mailbox access to read PTP clock time Milena Olech
2024-12-19  9:44 ` [PATCH v3 iwl-next 06/10] idpf: add PTP clock configuration Milena Olech
2024-12-19  9:44 ` [PATCH v3 iwl-next 07/10] idpf: add Tx timestamp capabilities negotiation Milena Olech
2024-12-19 15:05   ` Willem de Bruijn [this message]
2024-12-19  9:44 ` [PATCH v3 iwl-next 08/10] idpf: add Tx timestamp flows Milena Olech
2025-01-07 14:54   ` Willem de Bruijn
2025-01-10 16:45     ` Olech, Milena
2025-01-10 21:33       ` Willem de Bruijn
2025-01-13 18:08         ` Olech, Milena
2025-01-14 10:30           ` Willem de Bruijn
2024-12-19  9:44 ` [PATCH v3 iwl-next 09/10] idpf: add support for Rx timestamping Milena Olech
2024-12-19 15:01   ` Willem de Bruijn
2024-12-19  9:44 ` [PATCH v3 iwl-next 10/10] idpf: change the method for mailbox workqueue allocation Milena Olech

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=67643654983ec_1d0f5c29421@willemb.c.googlers.com.notmuch \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=emil.s.tantilov@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=milena.olech@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pavan.kumar.linga@intel.com \
    --cc=przemyslaw.kitszel@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