From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
alexandre.belloni@bootlin.com, horatiu.vultur@microchip.com,
f.fainelli@gmail.com, andrew@lunn.ch, vivien.didelot@gmail.com,
claudiu.manoil@nxp.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v2 net-next 0/2] Ocelot phylink fixes
Date: Fri, 20 Aug 2021 13:40:08 +0000 [thread overview]
Message-ID: <162946680863.23508.8493261893281323275.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210819164958.2244855-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 19 Aug 2021 19:49:56 +0300 you wrote:
> This series addresses a regression reported by Horatiu which introduced
> by the ocelot conversion to phylink: there are broken device trees in
> the wild, and the driver fails to probe the entire switch when a port
> fails to probe, which it previously did not do.
>
> Continue probing even when some ports fail to initialize properly.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] net: mscc: ocelot: be able to reuse a devlink_port after teardown
https://git.kernel.org/netdev/net-next/c/b5e33a157158
- [v2,net-next,2/2] net: mscc: ocelot: allow probing to continue with ports that fail to register
https://git.kernel.org/netdev/net-next/c/5c8bb71dbdf8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-08-20 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 16:49 [PATCH v2 net-next 0/2] Ocelot phylink fixes Vladimir Oltean
2021-08-19 16:49 ` [PATCH v2 net-next 1/2] net: mscc: ocelot: be able to reuse a devlink_port after teardown Vladimir Oltean
2021-08-19 16:49 ` [PATCH v2 net-next 2/2] net: mscc: ocelot: allow probing to continue with ports that fail to register Vladimir Oltean
2021-08-20 13:40 ` patchwork-bot+netdevbpf [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=162946680863.23508.8493261893281323275.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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.