From: Edward Cree <ecree.xilinx@gmail.com>
To: alejandro.lucero-palau@amd.com, netdev@vger.kernel.org,
linux-net-drivers@amd.com
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, habetsm.xilinx@gmail.com,
linux-doc@vger.kernel.org, corbet@lwn.net, jiri@nvidia.com
Subject: Re: [PATCH v5 net-next 3/8] sfc: enumerate mports in ef100
Date: Mon, 6 Feb 2023 12:38:03 +0000 [thread overview]
Message-ID: <fc2d452c-fa7f-39bb-b8bc-08e07ee9fbbc@gmail.com> (raw)
In-Reply-To: <20230202111423.56831-4-alejandro.lucero-palau@amd.com>
On 02/02/2023 11:14, alejandro.lucero-palau@amd.com wrote:
> From: Alejandro Lucero <alejandro.lucero-palau@amd.com>
>
> MAE ports (mports) are the ports on the EF100 embedded switch such
> as networking PCIe functions, the physical port, and potentially
> others.
>
> Signed-off-by: Alejandro Lucero <alejandro.lucero-palau@amd.com>
...
> +struct mae_mport_desc {
> + u32 mport_id;
> + u32 flags;
> + u32 caller_flags; /* enum mae_mport_desc_caller_flags */
> + u32 mport_type; /* MAE_MPORT_DESC_MPORT_TYPE_* */
> + union {
> + u32 port_idx; /* for mport_type == NET_PORT */
> + u32 alias_mport_id; /* for mport_type == ALIAS */
> + struct { /* for mport_type == VNIC */
> + u32 vnic_client_type; /* MAE_MPORT_DESC_VNIC_CLIENT_TYPE_* */
> + u32 interface_idx;
> + u16 pf_idx;
> + u16 vf_idx;
> + };
> + };
> + struct rhash_head linkage;
> + struct efx_rep *efv;
Looks like this isn't used or populated anywhere, so probably
shouldn't be added yet.
Apart from that, LGTM.
next prev parent reply other threads:[~2023-02-06 12:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 11:14 [PATCH v5 net-next 0/8] sfc: devlink support for ef100 alejandro.lucero-palau
2023-02-02 11:14 ` [PATCH v5 net-next 1/8] sfc: add " alejandro.lucero-palau
2023-02-02 11:50 ` Jiri Pirko
2023-02-06 12:00 ` Edward Cree
2023-02-07 14:21 ` Lucero Palau, Alejandro
2023-02-02 11:14 ` [PATCH v5 net-next 2/8] sfc: add devlink info " alejandro.lucero-palau
2023-02-02 11:58 ` Jiri Pirko
2023-02-07 14:42 ` Lucero Palau, Alejandro
2023-02-07 14:58 ` Jiri Pirko
2023-02-07 15:10 ` Lucero Palau, Alejandro
2023-02-07 17:24 ` Lucero Palau, Alejandro
2023-02-08 7:35 ` Jiri Pirko
2023-02-08 8:53 ` Lucero Palau, Alejandro
2023-02-03 2:37 ` kernel test robot
2023-02-03 11:38 ` kernel test robot
2023-02-02 11:14 ` [PATCH v5 net-next 3/8] sfc: enumerate mports in ef100 alejandro.lucero-palau
2023-02-06 12:38 ` Edward Cree [this message]
2023-02-07 15:14 ` Lucero Palau, Alejandro
2023-02-02 11:14 ` [PATCH v5 net-next 4/8] sfc: add mport lookup based on driver's mport data alejandro.lucero-palau
2023-02-02 11:14 ` [PATCH v5 net-next 5/8] sfc: add devlink port support for ef100 alejandro.lucero-palau
2023-02-02 12:01 ` Jiri Pirko
2023-02-06 14:02 ` Edward Cree
2023-02-07 15:20 ` Lucero Palau, Alejandro
2023-02-02 11:14 ` [PATCH v5 net-next 6/8] sfc: obtain device mac address based on firmware handle " alejandro.lucero-palau
2023-02-02 11:14 ` [PATCH v5 net-next 7/8] sfc: add support for devlink port_function_hw_addr_get in ef100 alejandro.lucero-palau
2023-02-02 12:09 ` Jiri Pirko
2023-02-07 15:01 ` Lucero Palau, Alejandro
2023-02-08 8:50 ` Lucero Palau, Alejandro
2023-02-02 11:14 ` [PATCH v5 net-next 8/8] sfc: add support for devlink port_function_hw_addr_set " alejandro.lucero-palau
2023-02-02 12:13 ` Jiri Pirko
2023-02-07 15:06 ` Lucero Palau, Alejandro
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=fc2d452c-fa7f-39bb-b8bc-08e07ee9fbbc@gmail.com \
--to=ecree.xilinx@gmail.com \
--cc=alejandro.lucero-palau@amd.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).