From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
<intel-wired-lan@lists.osuosl.org>,
<aleksander.lobakin@intel.com>
Cc: Wojciech Drewek <wojciech.drewek@intel.com>,
netdev@vger.kernel.org, Sai Krishna <saikrishnag@marvell.com>,
Ahmed Zaki <ahmed.zaki@intel.com>,
Simon Horman <horms@kernel.org>,
Jacob Keller <jacob.e.keller@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v9 06/14] iavf: add initial framework for registering PTP clock
Date: Thu, 15 Aug 2024 15:16:30 -0700 [thread overview]
Message-ID: <ae085a90-c786-52aa-2351-c7eabdc5292d@intel.com> (raw)
In-Reply-To: <20240813125513.8212-7-mateusz.polchlopek@intel.com>
On 8/13/2024 5:55 AM, Mateusz Polchlopek wrote:
> From: Jacob Keller <jacob.e.keller@intel.com>
...
> diff --git a/drivers/net/ethernet/intel/iavf/iavf_ptp.c b/drivers/net/ethernet/intel/iavf/iavf_ptp.c
...
> +static int iavf_ptp_register_clock(struct iavf_adapter *adapter)
> +{
> + struct ptp_clock_info *ptp_info = &adapter->ptp.info;
> + struct device *dev = &adapter->pdev->dev;
> +
> + memset(ptp_info, 0, sizeof(*ptp_info));
> +
> + snprintf(ptp_info->name, sizeof(ptp_info->name), "%s-%s-clk",
> + dev_driver_string(dev), dev_name(dev));
> + ptp_info->owner = THIS_MODULE;
> +
> + adapter->ptp.clock = ptp_clock_register(ptp_info, dev);
> + if (IS_ERR(adapter->ptp.clock)) {
> + adapter->ptp.clock = NULL;
> +
> + return PTR_ERR(adapter->ptp.clock);
> + }
cocci reports:
+drivers/net/ethernet/intel/iavf/iavf_ptp.c:47:9-16: ERROR: PTR_ERR
applied after initialization to constant on line 45
next prev parent reply other threads:[~2024-08-15 22:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 12:54 [Intel-wired-lan] [PATCH iwl-next v9 00/14] Add support for Rx timestamping for both ice and iavf drivers Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 01/14] virtchnl: add support for enabling PTP on iAVF Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 02/14] ice: support Rx timestamp on flex descriptor Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 03/14] virtchnl: add enumeration for the rxdid format Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 04/14] iavf: add support for negotiating flexible RXDID format Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 05/14] iavf: negotiate PTP capabilities Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 06/14] iavf: add initial framework for registering PTP clock Mateusz Polchlopek
2024-08-15 22:16 ` Tony Nguyen [this message]
2024-08-15 23:40 ` Keller, Jacob E
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 07/14] iavf: add support for indirect access to PHC time Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 08/14] iavf: periodically cache " Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 09/14] libeth: move idpf_rx_csum_decoded and idpf_rx_extracted Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 10/14] iavf: define Rx descriptors as qwords Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 11/14] iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 12/14] iavf: Implement checking DD desc field Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 13/14] iavf: handle set and get timestamps ops Mateusz Polchlopek
2024-08-13 12:55 ` [Intel-wired-lan] [PATCH iwl-next v9 14/14] iavf: add support for Rx timestamps to hotpath Mateusz Polchlopek
2024-08-15 22:16 ` [Intel-wired-lan] [PATCH iwl-next v9 00/14] Add support for Rx timestamping for both ice and iavf drivers Tony Nguyen
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=ae085a90-c786-52aa-2351-c7eabdc5292d@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@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=saikrishnag@marvell.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