mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Leon Romanovsky <leon@kernel.org>, Tariq Toukan <tariqt@nvidia.com>
Cc: Gal Pressman <gal@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
	 Saeed Mahameed <saeedm@nvidia.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	 "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	 netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH mlx5-next 0/2] mlx5-next updates 2025-02-19
Date: Sun, 23 Feb 2025 04:43:42 -0500	[thread overview]
Message-ID: <174030382258.497750.8800825927872509906.b4-ty@kernel.org> (raw)
In-Reply-To: <20250219085808.349923-1-tariqt@nvidia.com>


On Wed, 19 Feb 2025 10:58:06 +0200, Tariq Toukan wrote:
> This series contains mlx5 shared updates as preparation for upcoming
> features.
> 
> Regards,
> Tariq
> 
> Patrisious Haddad (1):
>   net/mlx5: Change POOL_NEXT_SIZE define value and make it global
> 
> [...]

Applied, thanks!

[1/2] net/mlx5: Add new health syndrome error and crr bit offset
      https://git.kernel.org/rdma/rdma/c/531ca2b9a215d0
[2/2] net/mlx5: Change POOL_NEXT_SIZE define value and make it global
      https://git.kernel.org/rdma/rdma/c/80df31f384b414

Best regards,
-- 
Leon Romanovsky <leon@kernel.org>


      parent reply	other threads:[~2025-02-23  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19  8:58 Tariq Toukan
2025-02-19  8:58 ` [PATCH mlx5-next 1/2] net/mlx5: Add new health syndrome error and crr bit offset Tariq Toukan
2025-02-19  8:58 ` [PATCH mlx5-next 2/2] net/mlx5: Change POOL_NEXT_SIZE define value and make it global Tariq Toukan
2025-02-23  9:43 ` Leon Romanovsky [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=174030382258.497750.8800825927872509906.b4-ty@kernel.org \
    --to=leon@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --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

all inboxes | Powered by JetHome®