All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Saeed Mahameed <saeed@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Jason Gunthorpe <jgg@nvidia.com>,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	Leon Romanovsky <leonro@nvidia.com>,
	Parav Pandit <parav@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
	Vu Pham <vuhuong@nvidia.com>, Saeed Mahameed <saeedm@nvidia.com>
Subject: Re: [net-next V6 02/14] devlink: Introduce PCI SF port flavour and port attribute
Date: Thu, 14 Jan 2021 09:42:30 -0800	[thread overview]
Message-ID: <20210114094230.67e8bef9@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20210113192730.280656-3-saeed@kernel.org>

On Wed, 13 Jan 2021 11:27:18 -0800 Saeed Mahameed wrote:
>  /**
>   * struct devlink_port_attrs - devlink port object
>   * @flavour: flavour of the port
> @@ -114,6 +126,7 @@ struct devlink_port_attrs {
>  		struct devlink_port_phys_attrs phys;
>  		struct devlink_port_pci_pf_attrs pci_pf;
>  		struct devlink_port_pci_vf_attrs pci_vf;
> +		struct devlink_port_pci_sf_attrs pci_sf;
>  	};
>  };

include/net/devlink.h:131: warning: Function parameter or member 'pci_sf' not described in 'devlink_port_attrs'

  reply	other threads:[~2021-01-14 17:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 19:27 [pull request][net-next V6 00/14] Add mlx5 subfunction support Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 01/14] devlink: Prepare code to fill multiple port function attributes Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 02/14] devlink: Introduce PCI SF port flavour and port attribute Saeed Mahameed
2021-01-14 17:42   ` Jakub Kicinski [this message]
2021-01-14 17:53     ` Parav Pandit
2021-01-14 18:22       ` Jakub Kicinski
2021-01-14 18:33         ` Parav Pandit
2021-01-13 19:27 ` [net-next V6 03/14] devlink: Support add and delete devlink port Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 04/14] devlink: Support get and set state of port function Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 05/14] net/mlx5: Introduce vhca state event notifier Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 06/14] net/mlx5: SF, Add auxiliary device support Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 07/14] net/mlx5: SF, Add auxiliary device driver Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 08/14] net/mlx5: E-switch, Prepare eswitch to handle SF vport Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 09/14] net/mlx5: E-switch, Add eswitch helpers for " Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 10/14] net/mlx5: SF, Add port add delete functionality Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 11/14] net/mlx5: SF, Port function state change support Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 12/14] devlink: Add devlink port documentation Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 13/14] devlink: Extend devlink port documentation for subfunctions Saeed Mahameed
2021-01-13 19:27 ` [net-next V6 14/14] net/mlx5: Add devlink subfunction port documentation Saeed Mahameed

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=20210114094230.67e8bef9@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jgg@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=parav@nvidia.com \
    --cc=saeed@kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=vuhuong@nvidia.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.