From: Sasha Levin <sashal@kernel.org>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Shay Drori <shayd@nvidia.com>,
"Anatoli.Chechelnickiy@m.interpipe.biz"
<Anatoli.Chechelnickiy@m.interpipe.biz>,
Saeed Mahameed <saeedm@nvidia.com>,
"oxana@cloudflare.com" <oxana@cloudflare.com>,
"leon@kernel.org" <leon@kernel.org>
Subject: Re: mlx5 driver fails to load in kernel 6.6.28
Date: Mon, 22 Apr 2024 19:10:33 -0400 [thread overview]
Message-ID: <ZibuaWod4Zvj0D4R@sashalap> (raw)
In-Reply-To: <ac75aa6b0f2485826bb530ffc7a78016881c7012.camel@nvidia.com>
On Mon, Apr 22, 2024 at 05:31:25PM +0000, Dragos Tatulea wrote:
>Hi,
>
> Based on the issue reported here [0], commit 0553e753ea9e ("net/mlx5: E-
>switch, store eswitch pointer before registering devlink_param") is missing from
>kernel 6.6.x due to a missing tag. Could you please include it in 6.6.x and
>6.8.x?
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2024-04-22 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 17:31 mlx5 driver fails to load in kernel 6.6.28 Dragos Tatulea
2024-04-22 23:10 ` Sasha Levin [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=ZibuaWod4Zvj0D4R@sashalap \
--to=sashal@kernel.org \
--cc=Anatoli.Chechelnickiy@m.interpipe.biz \
--cc=dtatulea@nvidia.com \
--cc=leon@kernel.org \
--cc=oxana@cloudflare.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=stable@vger.kernel.org \
/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