From: Jakub Kicinski <kuba@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Breno Leitao <leitao@debian.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
quic_jjohnson@quicinc.com, kvalo@kernel.org,
dennis.dalessandro@cornelisnetworks.com,
Jiri Pirko <jiri@resnulli.us>, Simon Horman <horms@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Coco Li <lixiaoyan@google.com>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Dennis Dalessandro <dennis.dalessandro@intel.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH net-next] net: create a dummy net_device allocator
Date: Tue, 2 Apr 2024 11:17:09 -0700 [thread overview]
Message-ID: <20240402111709.1551dbca@kernel.org> (raw)
In-Reply-To: <20240402180155.GM11187@unreal>
On Tue, 2 Apr 2024 21:01:55 +0300 Leon Romanovsky wrote:
> > Suggested-by: Jakub Kicinski <kuba@kernel.org>
> > Signed-off-by: Breno Leitao <leitao@debian.org>
>
> Exciting read for people who remember this conversation:
> """
> > I prefer to see some new wrapper over plain alloc_netdev, which will
> > create this dummy netdevice. For example, alloc_dummy_netdev(...).
>
> Nope, no bona fide APIs for hacky uses.
> """
> https://lore.kernel.org/linux-rdma/20240311112532.71f1cb35@kernel.org/
Still my preference, but there's only so many hours in the day
to keep explaining things. I'd rather we made some progress.
prev parent reply other threads:[~2024-04-02 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 20:08 [PATCH net-next] net: create a dummy net_device allocator Breno Leitao
2024-03-27 23:17 ` Jakub Kicinski
2024-03-28 14:57 ` Alexander Lobakin
2024-03-28 15:02 ` Alexander Lobakin
2024-03-28 17:10 ` Jakub Kicinski
2024-03-28 17:46 ` Breno Leitao
2024-03-28 17:40 ` Breno Leitao
2024-04-02 18:01 ` Leon Romanovsky
2024-04-02 18:17 ` Jakub Kicinski [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=20240402111709.1551dbca@kernel.org \
--to=kuba@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=dennis.dalessandro@intel.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kvalo@kernel.org \
--cc=leitao@debian.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_jjohnson@quicinc.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.