netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
	Jakub Kicinski <kuba@kernel.org>
Cc: Breno Leitao <leitao@debian.org>, Jason Gunthorpe <jgg@ziepe.ca>,
	"open list:HFI1 DRIVER" <linux-rdma@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] IB/hfi1: allocate dummy net_device dynamically
Date: Tue, 30 Apr 2024 17:10:39 +0300	[thread overview]
Message-ID: <20240430141039.GH100414@unreal> (raw)
In-Reply-To: <49973089-1e5e-48a2-9616-09cf8b8d5a7f@cornelisnetworks.com>

On Tue, Apr 30, 2024 at 10:03:49AM -0400, Dennis Dalessandro wrote:
> On 4/30/24 8:50 AM, Leon Romanovsky wrote:
> > On Fri, Apr 26, 2024 at 01:56:05AM -0700, Breno Leitao wrote:
> >> Embedding net_device into structures prohibits the usage of flexible
> >> arrays in the net_device structure. For more details, see the discussion
> >> at [1].
> >>
> >> Un-embed the net_device from struct hfi1_netdev_rx by converting it
> >> into a pointer. Then use the leverage alloc_netdev() to allocate the
> >> net_device object at hfi1_alloc_rx().
> >>
> >> [1] https://lore.kernel.org/all/20240229225910.79e224cf@kernel.org/
> >>
> >> Acked-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
> >> Signed-off-by: Breno Leitao <leitao@debian.org>
> >> ---
> >> Changelog
> >>
> >> v5:
> >> 	* Basically replaced the old alloc_netdev() by the new helper
> >> 	  alloc_netdev_dummy().
> >> v4:
> >> 	* Fix the changelog format
> >> v3:
> >> 	* Re-worded the comment, by removing the first paragraph.
> >> v2:
> >> 	* Free struct hfi1_netdev_rx allocation if alloc_netdev() fails
> >> 	* Pass zero as the private size for alloc_netdev().
> >> 	* Remove wrong reference for iwl in the comments
> >> ---
> >>
> >>  drivers/infiniband/hw/hfi1/netdev.h    | 2 +-
> >>  drivers/infiniband/hw/hfi1/netdev_rx.c | 9 +++++++--
> >>  2 files changed, 8 insertions(+), 3 deletions(-)
> > 
> > Dennis,
> > 
> > Do you plan to send anything to rdma-next which can potentially create
> > conflicts with netdev in this cycle?
> > 
> > If not, it will be safe to apply this patch directly to net-next.
> > 
> > Thanks
> 
> Nothing right now. Should be safe to sent to net-next.

Jakub, can you please take this patch?

> 
> FYI, since I talked about it publicly at the OFA Workshop recently. We will be
> starting the upstream of support for our new HW, soon.

Great, thanks

> 
> -Denny

  reply	other threads:[~2024-04-30 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240426085606.1801741-1-leitao@debian.org>
2024-04-30 12:50 ` [PATCH net-next] IB/hfi1: allocate dummy net_device dynamically Leon Romanovsky
2024-04-30 14:03   ` Dennis Dalessandro
2024-04-30 14:10     ` Leon Romanovsky [this message]
2024-04-30 14:55       ` Jakub Kicinski
2024-04-30 15:53         ` Breno Leitao

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=20240430141039.GH100414@unreal \
    --to=leon@kernel.org \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=jgg@ziepe.ca \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.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).