From: Jakub Kicinski <kuba@kernel.org>
To: Saeed Mahameed <saeed@kernel.org>
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,
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:48:19 -0700 [thread overview]
Message-ID: <20250821154819.249d6140@kernel.org> (raw)
In-Reply-To: <20250815194901.298689-1-saeed@kernel.org>
On Fri, 15 Aug 2025 12:48:57 -0700 Saeed Mahameed wrote:
> To: Saeed Mahameed <saeedm@nvidia.com>, Leon Romanovsky <leonro@nvidia.com>
> Subject: [GIT PULL][mlx5-next 0/4] Cached vhca id and adjacent function vports
> Hi Jakub, Jason,
Sorry for not pulling this easier. FWIW, I completely missed your
intent, IDK if Jason read your mind right. The series is tagged *for*
mlx5-next, and To: yourself and Leon. It totally looked like you're
planning to apply this to your mlx5-next tree and send it out as a PR
later. I missed the "Hi Jakub, Jason" :$
If in doubt please don't put any tree designation in the subject
prefix.
prev parent reply other threads:[~2025-08-21 22:48 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
2025-08-21 22:48 ` Jakub Kicinski [this message]
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=20250821154819.249d6140@kernel.org \
--to=kuba@kernel.org \
--cc=jgg@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 \
/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).