From: Tariq Toukan <ttoukan.linux@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Simon Horman <horms@kernel.org>, Tariq Toukan <tariqt@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Leon Romanovsky <leonro@nvidia.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
linux-rdma@vger.kernel.org, Itamar Gozlan <igozlan@nvidia.com>,
Yevgeny Kliteynik <kliteyn@nvidia.com>
Subject: Re: [PATCH net-next 10/12] net/mlx5: DR, add support for ConnectX-8 steering
Date: Sun, 15 Dec 2024 08:25:44 +0200 [thread overview]
Message-ID: <1e8c075c-2fd0-4d10-887d-04a5fb15baa2@gmail.com> (raw)
In-Reply-To: <20241212171134.52017f1e@kernel.org>
On 13/12/2024 3:11, Jakub Kicinski wrote:
> On Thu, 12 Dec 2024 20:31:30 +0200 Tariq Toukan wrote:
>> It requires pulling 4 IFC patches that were applied to
>> mlx5-next:
>> https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git/log/?h=mlx5-next
>
> What do you expect we'll do with this series?
>
> If you expect it to be set to Awaiting Upstream - could you make sure
> that the cover letter has "mlx5-next" in the subject? That will makes
> it easier to automate in patchwork.
>
The relevant patches have mlx5-next in their topic.
Should the cover letter as well?
What about other non-IFC patches, keep them with net-next?
> If you expect the series to be applied / merged - LMK, I can try
> to explain why that's impossible..
The motivation is to avoid potential conflicts with rdma trees.
AFAIK this is the agreed practice and is being followed for some time...
If not, what's the suggested procedure then?
How do you suggest getting these IFC changes to both net and rdma trees?
next prev parent reply other threads:[~2024-12-15 6:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 13:42 [PATCH net-next 00/12] mlx5 misc changes 2024-12-11 Tariq Toukan
2024-12-11 13:42 ` [PATCH mlx5-next 01/12] net/mlx5: Add device cap abs_native_port_num Tariq Toukan
2024-12-11 13:42 ` [PATCH net-next 02/12] net/mlx5: LAG, Refactor lag logic Tariq Toukan
2024-12-16 17:55 ` Alexander Lobakin
2024-12-17 5:44 ` rongwei liu
2024-12-17 11:32 ` Alexander Lobakin
2024-12-17 11:42 ` rongwei liu
2024-12-17 12:52 ` Mark Bloch
2024-12-17 15:03 ` Alexander Lobakin
2024-12-11 13:42 ` [PATCH net-next 03/12] net/mlx5: LAG, Support LAG over Multi-Host NICs Tariq Toukan
2024-12-11 13:42 ` [PATCH net-next 04/12] net/mlx5: fs, add counter object to flow destination Tariq Toukan
2024-12-12 17:20 ` Simon Horman
2024-12-12 18:32 ` Tariq Toukan
2024-12-11 13:42 ` [PATCH net-next 05/12] net/mlx5: fs, add mlx5_fs_pool API Tariq Toukan
2024-12-12 17:23 ` Simon Horman
2024-12-15 13:39 ` Moshe Shemesh
2024-12-18 5:22 ` Kees Cook
2024-12-18 8:21 ` Moshe Shemesh
2024-12-11 13:42 ` [PATCH net-next 06/12] net/mlx5: fs, retry insertion to hash table on EBUSY Tariq Toukan
2024-12-11 13:42 ` [PATCH net-next 07/12] net/mlx5: HWS, no need to expose mlx5hws_send_queues_open/close Tariq Toukan
2024-12-11 13:42 ` [PATCH net-next 08/12] net/mlx5: HWS, do not initialize native API queues Tariq Toukan
2024-12-11 13:42 ` [PATCH net-next 09/12] net/mlx5: DR, expand SWS STE callbacks and consolidate common structs Tariq Toukan
2024-12-11 13:42 ` [PATCH net-next 10/12] net/mlx5: DR, add support for ConnectX-8 steering Tariq Toukan
2024-12-12 17:31 ` Simon Horman
2024-12-12 18:31 ` Tariq Toukan
2024-12-13 1:11 ` Jakub Kicinski
2024-12-15 6:25 ` Tariq Toukan [this message]
2024-12-15 21:12 ` Jakub Kicinski
2024-12-16 12:50 ` Tariq Toukan
2024-12-13 10:31 ` Simon Horman
2024-12-11 13:42 ` [PATCH net-next 11/12] net/mlx5: Remove PTM support log message Tariq Toukan
2024-12-11 13:42 ` [PATCH net-next 12/12] net/mlx5: fs, Add support for RDMA RX steering over IB link layer Tariq Toukan
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=1e8c075c-2fd0-4d10-887d-04a5fb15baa2@gmail.com \
--to=ttoukan.linux@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=igozlan@nvidia.com \
--cc=kliteyn@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=saeedm@nvidia.com \
--cc=tariqt@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