[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161351340855.15084.15305513018213877507.git-patchwork-notify@kernel.org>
Date: Tue, 16 Feb 2021 22:10:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Vladimir Oltean <olteanv@...il.com>
Cc: davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
andrew@...n.ch, f.fainelli@...il.com, vivien.didelot@...il.com,
claudiu.manoil@....com, alexandre.belloni@...tlin.com,
UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH net-next] net: dsa: felix: perform teardown on error in
felix_setup
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 16 Feb 2021 13:32:13 +0200 you wrote:
> From: Vladimir Oltean <vladimir.oltean@....com>
>
> If the driver fails to probe, it would be nice to not leak memory.
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>
> ---
> I've decided to target this patch towards net-next because:
> - no user has complained about this being an issue
> - in theory there should be a Fixes: 56051948773e ("net: dsa: ocelot:
> add driver for Felix switch family") but the fix already conflicts
> with some patches that are in net-next:
> * f59fd9cab730 ("net: mscc: ocelot: configure watermarks using devlink-sb")
> * c54913c1d4ee ("net: dsa: ocelot: request DSA to fix up lack of address learning on CPU port")
> and it would unnecessarily cause maintainance headaches to resolve the
> conflicts.
> Alternatively I could wait until net-next is merged into net and send
> the bugfix at that point, but the result would be the same: the patch
> would not be backportable basically anywhere.
>
> [...]
Here is the summary with links:
- [net-next] net: dsa: felix: perform teardown on error in felix_setup
https://git.kernel.org/netdev/net-next/c/6b73b7c96a91
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists