From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
johannes@sipsolutions.net, pablo@netfilter.org,
laforge@gnumonks.org, Jason@zx2c4.com, jgg@nvidia.com,
leonro@nvidia.com
Subject: Re: [RFC net-next] net: add ndo_alloc_and_init and ndo_release to replace priv_destructor
Date: Wed, 11 May 2022 14:11:33 -0700 [thread overview]
Message-ID: <20220511141133.142f2a45@kernel.org> (raw)
In-Reply-To: <20220511191218.1402380-1-kuba@kernel.org>
On Wed, 11 May 2022 12:12:18 -0700 Jakub Kicinski wrote:
> That's best I can come up. Using .ndo_free as a name may seem
> like a better option but that may make people think it's called
> from free_netdev().
Maybe ndo_destroy is better 🤔
next prev parent reply other threads:[~2022-05-11 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 19:12 [RFC net-next] net: add ndo_alloc_and_init and ndo_release to replace priv_destructor Jakub Kicinski
2022-05-11 21:11 ` Jakub Kicinski [this message]
2022-05-11 23:43 ` Jason Gunthorpe
2022-05-13 5:47 ` Leon Romanovsky
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=20220511141133.142f2a45@kernel.org \
--to=kuba@kernel.org \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@nvidia.com \
--cc=johannes@sipsolutions.net \
--cc=laforge@gnumonks.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
/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;
as well as URLs for NNTP newsgroup(s).