regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Paul Moore <paul@paul-moore.com>,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	Saeed Mahameed <saeed@kernel.org>, Shay Drory <shayd@nvidia.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	netdev@vger.kernel.org, selinux@vger.kernel.org,
	Tariq Toukan <tariqt@nvidia.com>
Subject: Re: Potential regression/bug in net/mlx5 driver
Date: Thu, 13 Apr 2023 07:54:21 -0700	[thread overview]
Message-ID: <20230413075421.044d7046@kernel.org> (raw)
In-Reply-To: <20230410054605.GL182481@unreal>

On Mon, 10 Apr 2023 08:46:05 +0300 Leon Romanovsky wrote:
> > I haven't seen any updates from the mlx5 driver folks, although I may
> > not have been CC'd?  
> 
> We are extremely slow these days due to combination of holidays
> (Easter, Passover, Ramadan, spring break e.t.c).

Let's get this fixed ASAP, please. I understand that there are
holidays, but it's been over 2 weeks, and addressing regressions
should be highest priority for any maintainer! :(

From what I gather all we need here is to throw in an extra condition
for "FW is hella old" into mlx5_core_is_management_pf(), no?

  parent reply	other threads:[~2023-04-13 14:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 23:08 Potential regression/bug in net/mlx5 driver Paul Moore
2023-03-29 22:20 ` Saeed Mahameed
2023-03-30  1:27   ` Paul Moore
2023-04-09  8:48     ` Linux regression tracking (Thorsten Leemhuis)
2023-04-09 23:50       ` Paul Moore
2023-04-10  5:46         ` Leon Romanovsky
2023-04-13 13:49           ` Linux regression tracking (Thorsten Leemhuis)
2023-04-13 14:54           ` Jakub Kicinski [this message]
2023-04-13 15:19             ` Paul Moore
2023-04-13 21:12               ` Saeed Mahameed
2023-04-13 22:21                 ` Jakub Kicinski
2023-04-13 22:34                   ` Saeed Mahameed
2023-04-13 22:51                     ` Jakub Kicinski
2023-04-14  3:03                       ` Saeed Mahameed
2023-04-14  3:26                         ` Jakub Kicinski
2023-04-14 14:37                           ` Paul Moore
2023-04-14 22:20                           ` Saeed Mahameed
2023-04-15  0:34                             ` Jakub Kicinski
2023-04-15  4:40                               ` Saeed Mahameed
2023-04-17 15:38                                 ` Jakub Kicinski
2023-04-20  0:43                                   ` Saeed Mahameed
2023-04-20  0:46                                     ` Jakub Kicinski
2023-04-20  4:02                                       ` Saeed Mahameed
2023-03-31 13:10 ` Linux regression tracking #adding (Thorsten Leemhuis)

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=20230413075421.044d7046@kernel.org \
    --to=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=regressions@lists.linux.dev \
    --cc=saeed@kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=selinux@vger.kernel.org \
    --cc=shayd@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;
as well as URLs for NNTP newsgroup(s).