All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Elad Nachman <enachman@marvell.com>,
	Taras Chornyi <taras.chornyi@plvision.eu>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
	"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
	"przemyslaw.kitszel@intel.com" <przemyslaw.kitszel@intel.com>,
	"dkirjanov@suse.de" <dkirjanov@suse.de>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXTERNAL] Re: [PATCH v2 0/5] Fix prestera driver fail to probe twice
Date: Mon, 25 Mar 2024 14:04:11 +0100	[thread overview]
Message-ID: <7c79b1f8-a5b6-46b7-99fc-a0ac1bec5694@lunn.ch> (raw)
In-Reply-To: <20240325134537.1cc7560e@kmaincent-XPS-13-7390>

> Prestera is indeed not directly involved in PoE. I wrote a hack to be able to
> get the PoE ports control, for testing my PoE patch series.
> 
> The aim in the future will be to add RJ45 port abstraction.
> The Prestera will get the port abstraction which will get the PoE ports control.
> The prestera driver then might receive an EPROBE_DEFER from it.

O.K, so EPRODE_DEFER has to work in a meaningful way. I'm not sure we
can call a 30 second delay meaningful.

And it is not just PoE. phylink_create() can return EPROBE_DEFER, and
there are probably others.

      Andrew

  reply	other threads:[~2024-03-25 13:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 17:20 [PATCH v2 0/5] Fix prestera driver fail to probe twice Elad Nachman
2024-03-20 17:20 ` [PATCH v2 1/5] net: marvell: prestera: fix driver reload Elad Nachman
2024-03-20 22:58   ` Andrew Lunn
2024-03-21 17:22     ` [EXTERNAL] " Elad Nachman
2024-03-20 17:20 ` [PATCH v2 2/5] net: marvell: prestera: enlarge fw restart time Elad Nachman
2024-03-21  0:10   ` Andrew Lunn
2024-03-21 17:24     ` [EXTERNAL] " Elad Nachman
2024-03-20 17:20 ` [PATCH v2 3/5] net: marvell: prestera: fix memory use after free Elad Nachman
2024-03-21  0:14   ` Andrew Lunn
2024-03-20 17:20 ` [PATCH v2 4/5] net: marvell: prestera: force good base mac Elad Nachman
2024-03-21  0:13   ` Andrew Lunn
2024-03-20 17:20 ` [PATCH v2 5/5] net: marvell: prestera: unbind sfp port on exit Elad Nachman
2024-03-21  0:13   ` Andrew Lunn
2024-03-21  0:18 ` [PATCH v2 0/5] Fix prestera driver fail to probe twice Andrew Lunn
2024-03-21 17:33   ` [EXTERNAL] " Elad Nachman
2024-03-21 19:22     ` Andrew Lunn
2024-03-24  7:53       ` Elad Nachman
2024-03-24 15:25         ` Andrew Lunn
2024-03-25 12:45           ` Kory Maincent
2024-03-25 13:04             ` Andrew Lunn [this message]
2024-03-27 17:27           ` Elad Nachman
2024-03-21  9:06 ` Kory Maincent
2024-03-21 15:53   ` Jakub Kicinski

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=7c79b1f8-a5b6-46b7-99fc-a0ac1bec5694@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dkirjanov@suse.de \
    --cc=edumazet@google.com \
    --cc=enachman@marvell.com \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.