public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next 0/2] Remove ancient qib driver
Date: Wed, 28 May 2025 20:24:23 +0300	[thread overview]
Message-ID: <20250528172423.GB7435@unreal> (raw)
In-Reply-To: <a52bb580-4ebd-4e82-b584-a597483da862@cornelisnetworks.com>

On Wed, May 28, 2025 at 10:32:19AM -0400, Dennis Dalessandro wrote:
> On 5/28/25 8:11 AM, Leon Romanovsky wrote:
> > On Tue, May 27, 2025 at 11:46:02AM -0400, Dennis Dalessandro wrote:
> >> Time for qib to go bye-bye.
> > 
> > Thanks for doing this, it is too bad that you sent it during merge window.
> 
> No rush on this. I meant to send it a while back but kept getting preempted.
> 
> > BTW, can we get rid of rdmavt later too? Do you plan to reuse it?
> 
> We *could* wedge it back into hfi1 but I don't think that really gains us much
> and it will actually be expanded as we begin to add Ethernet/RoCE support which
> will be coming soon.

At least from my side, "rdmavt" removal is a nice to have, but definitely not must.

Thanks

> 
> -Denny
> 
> 

  reply	other threads:[~2025-05-28 17:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 15:46 [PATCH for-next 0/2] Remove ancient qib driver Dennis Dalessandro
2025-05-27 15:46 ` [PATCH for-next 1/2] RDMA/qib: Remove outdated driver Dennis Dalessandro
2025-05-27 15:46 ` [PATCH for-next 2/2] Maintainers: Remove QIB Dennis Dalessandro
2025-05-28 12:11 ` [PATCH for-next 0/2] Remove ancient qib driver Leon Romanovsky
2025-05-28 14:32   ` Dennis Dalessandro
2025-05-28 17:24     ` Leon Romanovsky [this message]
2025-06-12  7:50 ` Leon Romanovsky
2025-06-17 17:09 ` Jason Gunthorpe

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=20250528172423.GB7435@unreal \
    --to=leon@kernel.org \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@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