From: Jakub Kicinski <kuba@kernel.org>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Cc: Wojciech Drewek <wojciech.drewek@intel.com>,
netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
horms@kernel.org, Jacob Keller <jacob.e.keller@intel.com>,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v3 05/12] iavf: negotiate PTP capabilities
Date: Wed, 3 Apr 2024 18:47:46 -0700 [thread overview]
Message-ID: <20240403184746.178b2268@kernel.org> (raw)
In-Reply-To: <20240403131927.87021-6-mateusz.polchlopek@intel.com>
On Wed, 3 Apr 2024 09:19:20 -0400 Mateusz Polchlopek wrote:
> --- a/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c
> +++ b/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c
> @@ -145,6 +145,7 @@ int iavf_send_vf_config_msg(struct iavf_adapter *adapter)
> VIRTCHNL_VF_OFFLOAD_CRC |
> VIRTCHNL_VF_OFFLOAD_ENCAP_CSUM |
> VIRTCHNL_VF_OFFLOAD_REQ_QUEUES |
> + VIRTCHNL_VF_CAP_PTP |
> VIRTCHNL_VF_OFFLOAD_ADQ |
coccicheck says VIRTCHNL_VF_CAP_PTP ends up on this list twice.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
horms@kernel.org, anthony.l.nguyen@intel.com,
Jacob Keller <jacob.e.keller@intel.com>,
Wojciech Drewek <wojciech.drewek@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v3 05/12] iavf: negotiate PTP capabilities
Date: Wed, 3 Apr 2024 18:47:46 -0700 [thread overview]
Message-ID: <20240403184746.178b2268@kernel.org> (raw)
In-Reply-To: <20240403131927.87021-6-mateusz.polchlopek@intel.com>
On Wed, 3 Apr 2024 09:19:20 -0400 Mateusz Polchlopek wrote:
> --- a/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c
> +++ b/drivers/net/ethernet/intel/iavf/iavf_virtchnl.c
> @@ -145,6 +145,7 @@ int iavf_send_vf_config_msg(struct iavf_adapter *adapter)
> VIRTCHNL_VF_OFFLOAD_CRC |
> VIRTCHNL_VF_OFFLOAD_ENCAP_CSUM |
> VIRTCHNL_VF_OFFLOAD_REQ_QUEUES |
> + VIRTCHNL_VF_CAP_PTP |
> VIRTCHNL_VF_OFFLOAD_ADQ |
coccicheck says VIRTCHNL_VF_CAP_PTP ends up on this list twice.
next prev parent reply other threads:[~2024-04-04 1:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 13:19 [Intel-wired-lan] [PATCH iwl-next v3 00/12] Add support for Rx timestamping for both ice and iavf drivers Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 01/12] virtchnl: add support for enabling PTP on iAVF Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 02/12] ice: support Rx timestamp on flex descriptor Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 03/12] virtchnl: add enumeration for the rxdid format Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 04/12] iavf: add support for negotiating flexible RXDID format Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 05/12] iavf: negotiate PTP capabilities Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-04 1:47 ` Jakub Kicinski [this message]
2024-04-04 1:47 ` Jakub Kicinski
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 06/12] iavf: add initial framework for registering PTP clock Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 07/12] iavf: add support for indirect access to PHC time Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 08/12] iavf: periodically cache " Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 09/12] iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 10/12] iavf: Implement checking DD desc field Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 11/12] iavf: handle SIOCSHWTSTAMP and SIOCGHWTSTAMP Mateusz Polchlopek
2024-04-03 13:19 ` Mateusz Polchlopek
2024-04-03 13:19 ` [Intel-wired-lan] [PATCH iwl-next v3 12/12] iavf: add support for Rx timestamps to hotpath Mateusz Polchlopek
2024-04-03 13:19 ` 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=20240403184746.178b2268@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=netdev@vger.kernel.org \
--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 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.