From: Roger Quadros <rogerq@kernel.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 2/2] net: ethernet: ti: am65-cpsw: avoid devm_alloc_etherdev, fix module removal
Date: Mon, 7 Oct 2024 14:37:15 +0300 [thread overview]
Message-ID: <48ca3541-df4a-4215-b81b-80d6ed8145c3@kernel.org> (raw)
In-Reply-To: <500r48s9-6s4o-ppnr-4p2q-05731rnn9qs6@syhkavp.arg>
On 05/10/2024 23:26, Nicolas Pitre wrote:
> On Fri, 4 Oct 2024, Roger Quadros wrote:
>
>>> If you know of a way to do this differently I'm all ears.
>>
>> I sent another approach already. please check.
>> https://lore.kernel.org/all/67c9ede4-9751-4255-b752-27dd60495ff3@kernel.org/
>
> Seems to work correctly.
>
> Still... given this paragraph found in Documentation/process/maintainer-netdev.rst:
>
> |Netdev remains skeptical about promises of all "auto-cleanup" APIs,
> |including even ``devm_`` helpers, historically. They are not the preferred
> |style of implementation, merely an acceptable one.
>
> and given my solution is way simpler, I tend to also prefer it over yours.
OK. Let's go with yours as it makes the driver more compliant to netdev
guidelines.
>
> But I'm not the maintainer nor even a significant contributor here so as
> long as the issue is fixed I won't mind.
>
>>> About the many error cases needing the freeing of net devices, as far as
>>> I know they're all covered with this patch.
>>
>> No they are not.
>
> As I said yesterday, I do still stand by my affirmation that they are.
> Please look at the entire return path and you'll see that everything is
> covered.
Indeed, my bad. It wasn't obvious by just looking at the patch but when looking at
the code it is called via am65_cpsw_nuss_cleanup_ndev().
>
>
> Nicolas
--
cheers,
-roger
next prev parent reply other threads:[~2024-10-07 11:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 4:10 [PATCH net v3 0/2] fix ti-am65-cpsw-nuss " Nicolas Pitre
2024-10-04 4:10 ` [PATCH net v3 1/2] net: ethernet: ti: am65-cpsw: prevent WARN_ON upon " Nicolas Pitre
2024-10-04 8:48 ` Roger Quadros
2024-10-04 4:10 ` [PATCH net v3 2/2] net: ethernet: ti: am65-cpsw: avoid devm_alloc_etherdev, fix " Nicolas Pitre
2024-10-04 9:09 ` Roger Quadros
2024-10-04 12:57 ` Roger Quadros
2024-10-04 15:37 ` Nicolas Pitre
2024-10-04 19:50 ` Roger Quadros
2024-10-04 21:17 ` Nicolas Pitre
2024-10-05 20:26 ` Nicolas Pitre
2024-10-07 11:37 ` Roger Quadros [this message]
2024-10-07 11:37 ` Roger Quadros
2024-10-08 8:50 ` [PATCH net v3 0/2] fix ti-am65-cpsw-nuss " patchwork-bot+netdevbpf
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=48ca3541-df4a-4215-b81b-80d6ed8145c3@kernel.org \
--to=rogerq@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=grygorii.strashko@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=pabeni@redhat.com \
--cc=vigneshr@ti.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
Powered by JetHome