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, Dean Luick <dean.luick@cornelisnetworks.com>,
	linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next 0/4] Prepare for hfi2 submission
Date: Tue, 10 Mar 2026 20:00:26 +0200	[thread overview]
Message-ID: <20260310180026.GE12611@unreal> (raw)
In-Reply-To: <9c9ffd7b-0124-4d72-a894-4498b7c44f96@cornelisnetworks.com>

On Tue, Mar 10, 2026 at 10:14:55AM -0400, Dennis Dalessandro wrote:
> On 3/10/26 7:08 AM, Leon Romanovsky wrote:
> > On Mon, Mar 09, 2026 at 04:44:39PM -0400, Dennis Dalessandro wrote:
> > > These 4 patches get rdmavt ready for hfi2 support. This is being split out
> > > from the previous patch submission [1].
> > > 
> > > [1] https://lore.kernel.org/linux-rdma/175129726945.1859400.4492277779101226937.stgit@awdrv-04.cornelisnetworks.com/
> > > 
> > > ---
> > > 
> > > Dean Luick (4):
> > >        RDMA/OPA: Update OPA link speed list
> > >        RDMA/rdmavt: Add ucontext alloc/dealloc passthrough
> > >        RDMA/rdmavt: Correct multi-port QP iteration
> > >        RDMA/rdmavt: Add driver mmap callback
> > 
> > Something went wrong, second patch didn't arrive.
> > https://lore.kernel.org/all/177308892140.1279894.3475429390519673020.stgit@awdrv-04.cornelisnetworks.com/
> 
> Sorry about that, I'm working the problem with our IT dept right now. The
> mailserver decided to eat half of my patches.

In the meantime, I can take these three patches if you prefer.

By the way, these patches currently have no in-kernel consumers, but
let's assume you plan to use them in your hfi2 driver."

Thanks

> 
> -Denny

  reply	other threads:[~2026-03-10 18:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 20:44 [PATCH for-next 0/4] Prepare for hfi2 submission Dennis Dalessandro
2026-03-09 20:44 ` [PATCH for-next 1/4] RDMA/OPA: Update OPA link speed list Dennis Dalessandro
2026-03-09 20:44 ` [PATCH for-next 3/4] RDMA/rdmavt: Correct multi-port QP iteration Dennis Dalessandro
2026-03-09 20:44 ` [PATCH for-next 4/4] RDMA/rdmavt: Add driver mmap callback Dennis Dalessandro
2026-03-10 11:08 ` [PATCH for-next 0/4] Prepare for hfi2 submission Leon Romanovsky
2026-03-10 14:14   ` Dennis Dalessandro
2026-03-10 18:00     ` Leon Romanovsky [this message]
2026-03-11 17:28 ` [PATCH for-next 2/4] RDMA/rdmavt: Add ucontext alloc/dealloc passthrough Dennis Dalessandro
2026-03-11 19:17 ` [PATCH for-next 0/4] Prepare for hfi2 submission 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=20260310180026.GE12611@unreal \
    --to=leon@kernel.org \
    --cc=dean.luick@cornelisnetworks.com \
    --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