* [PATCH] net: ti: icssg-prueth: Add missing icss_iep_put to error path
@ 2023-11-02 16:03 Jan Kiszka
2023-11-04 18:43 ` Simon Horman
0 siblings, 1 reply; 2+ messages in thread
From: Jan Kiszka @ 2023-11-02 16:03 UTC (permalink / raw)
To: David S. Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni,
MD Danish Anwar
Cc: netdev, linux-kernel, Lopes Ivo, Diogo Miguel (T CED IFD-PT),
Nishanth Menon, Su, Bao Cheng (RC-CN DF FA R&D)
From: Jan Kiszka <jan.kiszka@siemens.com>
Analogously to prueth_remove.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
This was lost from the TI SDK version while ripping out SR1.0 support -
which we are currently restoring for upstream.
drivers/net/ethernet/ti/icssg/icssg_prueth.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/ethernet/ti/icssg/icssg_prueth.c b/drivers/net/ethernet/ti/icssg/icssg_prueth.c
index ffae89a6ccc5..0242e123fc05 100644
--- a/drivers/net/ethernet/ti/icssg/icssg_prueth.c
+++ b/drivers/net/ethernet/ti/icssg/icssg_prueth.c
@@ -2200,6 +2200,9 @@ static int prueth_probe(struct platform_device *pdev)
if (prueth->pdata.quirk_10m_link_issue)
icss_iep_exit_fw(prueth->iep1);
+ icss_iep_put(prueth->iep1);
+ icss_iep_put(prueth->iep0);
+
free_pool:
gen_pool_free(prueth->sram_pool,
(unsigned long)prueth->msmcram.va, msmc_ram_size);
--
2.35.3
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] net: ti: icssg-prueth: Add missing icss_iep_put to error path
2023-11-02 16:03 [PATCH] net: ti: icssg-prueth: Add missing icss_iep_put to error path Jan Kiszka
@ 2023-11-04 18:43 ` Simon Horman
0 siblings, 0 replies; 2+ messages in thread
From: Simon Horman @ 2023-11-04 18:43 UTC (permalink / raw)
To: Jan Kiszka
Cc: David S. Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni,
MD Danish Anwar, netdev, linux-kernel,
Lopes Ivo, Diogo Miguel (T CED IFD-PT), Nishanth Menon,
Su, Bao Cheng (RC-CN DF FA R&D)
On Thu, Nov 02, 2023 at 05:03:30PM +0100, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Analogously to prueth_remove.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Hi Jan,
I am a little unclear if this patch addresses a user-visible bug, or
is adding a new feature.
If it is fixing a bug then it should be targeted at the net tree.
It should apply cleanly there, and the tree should be noted in the subject.
Subject: [PATCH net] ...
Also, if it is a bug fix, it should have a fixes tag, indicating the
revision(s) where the problem was introduced. This to assist in backporting
fixes. In this case perhaps the following is appropriate:
On the other hand, if this is a new feature, then it should be targeted
at net-next:
Subject: [PATCH net-next] ...
And in that case the following applies.
In either case, I think it would be good to expand the commit message.
It should explain why this change is being made.
## Form letter - net-next-closed
The merge window for v6.7 has begun and therefore net-next is closed
for new drivers, features, code refactoring and optimizations.
We are currently accepting bug fixes only.
Please repost when net-next reopens after November 12th.
RFC patches sent for review only are obviously welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: cr
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-11-04 18:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-11-02 16:03 [PATCH] net: ti: icssg-prueth: Add missing icss_iep_put to error path Jan Kiszka
2023-11-04 18:43 ` Simon Horman
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).