netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Elad Nachman <enachman@marvell.com>
Cc: "Köry Maincent" <kory.maincent@bootlin.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Taras Chornyi" <taras.chornyi@plvision.eu>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Miquel Raynal" <miquel.raynal@bootlin.com>
Subject: Re: [EXT] Prestera driver fail to probe twice
Date: Mon, 12 Feb 2024 16:29:32 -0800	[thread overview]
Message-ID: <20240212162932.3b438657@kernel.org> (raw)
In-Reply-To: <20240208073718.7fcb93d4@kernel.org>

On Thu, 8 Feb 2024 07:37:18 -0800 Jakub Kicinski wrote:
> On Thu, 8 Feb 2024 07:36:54 +0000 Elad Nachman wrote:
> > Once again, existing deployed firmware does not check the enum below,
> > so this does not ensure backward compatibility.  
> 
> Okay, if it's a bigger rework - how much time do you need to get
> it fixed?

This question is hogging a spot on my todo list.
I'll earmark the driver for removal in three months if there's 
no progress. Please LMK if you have a different estimate.
It's just a question of it not falling thru the cracks.

  reply	other threads:[~2024-02-13  0:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 15:54 Prestera driver fail to probe twice Köry Maincent
2024-02-06 18:30 ` [EXT] " Elad Nachman
2024-02-07 10:22   ` Köry Maincent
2024-02-07 10:56     ` Elad Nachman
2024-02-07 11:28       ` Köry Maincent
2024-02-07 12:24         ` Elad Nachman
2024-02-07 14:31           ` Köry Maincent
2024-02-07 15:06             ` Elad Nachman
2024-02-07 18:31               ` Jakub Kicinski
2024-02-08  7:36                 ` Elad Nachman
2024-02-08 15:37                   ` Jakub Kicinski
2024-02-13  0:29                     ` Jakub Kicinski [this message]
2024-02-07 23:32 ` Andrew Lunn
2024-02-08  9:10   ` Köry Maincent
2024-02-08 14:56     ` Andrew Lunn

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=20240212162932.3b438657@kernel.org \
    --to=kuba@kernel.org \
    --cc=enachman@marvell.com \
    --cc=kory.maincent@bootlin.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=taras.chornyi@plvision.eu \
    --cc=thomas.petazzoni@bootlin.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).