From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1 01/13] ixgbe: add initial devlink support
Date: Thu, 6 Feb 2025 13:39:48 -0800 [thread overview]
Message-ID: <75ad6505-3d74-4d1a-a0ee-5d028c1bc0df@intel.com> (raw)
In-Reply-To: <20250203150328.4095-2-jedrzej.jagielski@intel.com>
On 2/3/2025 7:03 AM, Jedrzej Jagielski wrote:
> Add an initial support for devlink interface to ixgbe driver.
>
> Similarly to i40e driver the implementation doesn't enable
> devlink to manage device-wide configuration. Devlink instance
> is created for each physical function of PCIe device.
>
> Create separate directory for devlink related ixgbe files
> and use naming scheme similar to the one used in the ice driver.
>
> Add a stub for Documentation, to be extended by further patches.
>
> Reviewed-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
> Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
...
> @@ -11283,6 +11284,10 @@ static int ixgbe_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
> goto err_ioremap;
> }
>
> + err = ixgbe_allocate_devlink(adapter);
> + if (err)
> + goto err_ioremap;
Looks like the unroll has an issue.
Smatch reports:
../drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:11844 ixgbe_probe()
warn: 'hw->hw_addr' from ioremap() not released on lines: 11844.
Thanks,
Tony
> +
> netdev->netdev_ops = &ixgbe_netdev_ops;
> ixgbe_set_ethtool_ops(netdev);
> netdev->watchdog_timeo = 5 * HZ;
next prev parent reply other threads:[~2025-02-06 21:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 15:03 [Intel-wired-lan] [PATCH iwl-next v1 00/13] ixgbe: Add basic devlink support Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 01/13] ixgbe: add initial " Jedrzej Jagielski
2025-02-06 21:39 ` Tony Nguyen [this message]
2025-02-07 10:47 ` Simon Horman
2025-02-10 11:08 ` Jagielski, Jedrzej
2025-02-09 11:13 ` Simon Horman
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 02/13] ixgbe: add handler for devlink .info_get() Jedrzej Jagielski
2025-02-09 16:27 ` Simon Horman
2025-02-10 11:06 ` Jagielski, Jedrzej
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 03/13] ixgbe: add E610 functions for acquiring flash data Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 04/13] ixgbe: read the OROM version information Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 05/13] ixgbe: read the netlist " Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 06/13] ixgbe: add .info_get extension specific for E610 devices Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 07/13] ixgbe: add E610 functions getting PBA and FW ver info Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 08/13] ixgbe: extend .info_get with stored versions Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 09/13] ixgbe: add device flash update via devlink Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 10/13] ixgbe: add support for devlink reload Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 11/13] ixgbe: add FW API version check Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 12/13] ixgbe: add E610 implementation of FW recovery mode Jedrzej Jagielski
2025-02-03 15:03 ` [Intel-wired-lan] [PATCH iwl-next v1 13/13] ixgbe: add support for FW rollback mode Jedrzej Jagielski
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=75ad6505-3d74-4d1a-a0ee-5d028c1bc0df@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jedrzej.jagielski@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=netdev@vger.kernel.org \
/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