From: Saeed Mahameed <saeed@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>, Parav Pandit <parav@nvidia.com>
Subject: Re: [GIT PULL][mlx5-next 0/4] Cached vhca id and adjacent function vports
Date: Thu, 21 Aug 2025 15:19:47 -0700 [thread overview]
Message-ID: <aKebg86MTNxhegvZ@x130> (raw)
In-Reply-To: <c263ea0a-adb3-4c91-81b8-cb5b283c5806@redhat.com>
On 21 Aug 10:37, Paolo Abeni wrote:
>On 8/15/25 9:48 PM, Saeed Mahameed wrote:
>> From: Saeed Mahameed <saeedm@nvidia.com>
>>
>> Hi Jakub, Jason,
>>
>> This pull request introduces a preparation patchset for caching vhca_id
>> and needed HW bits for the upcoming netdev/eswitch series to support
>> adjacent function vports.
>>
>> For more information please see tag log below.
>
>This has a conflict vs net-next, could you please double check the
>conflict resolution?
Looks good, Thank you Paolo.
>
>Thanks,
>
>Paolo
>
next prev parent reply other threads:[~2025-08-21 22:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 19:48 [GIT PULL][mlx5-next 0/4] Cached vhca id and adjacent function vports Saeed Mahameed
2025-08-15 19:48 ` [PATCH mlx5-next 1/4] net/mlx5: mlx5_ifc, Add hardware definitions needed for adjacent vports Saeed Mahameed
2025-08-15 19:48 ` [PATCH mlx5-next 2/4] net/mlx5: E-Switch, Cache vport vhca id on first cap query Saeed Mahameed
2025-08-15 19:49 ` [PATCH mlx5-next 3/4] net/mlx5: E-Switch, Set/Query hca cap via vhca id Saeed Mahameed
2025-09-11 22:59 ` Jakub Kicinski
2025-08-15 19:49 ` [PATCH mlx5-next 4/4] {rdma,net}/mlx5: export mlx5_vport_get_vhca_id Saeed Mahameed
2025-08-21 8:37 ` [GIT PULL][mlx5-next 0/4] Cached vhca id and adjacent function vports Paolo Abeni
2025-08-21 22:19 ` Saeed Mahameed [this message]
2025-08-21 22:48 ` Jakub Kicinski
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=aKebg86MTNxhegvZ@x130 \
--to=saeed@kernel.org \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox