From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: Patrick Kelsey <pat.kelsey@cornelisnetworks.com>,
Douglas Miller <doug.miller@cornelisnetworks.com>,
Brendan Cunningham <bcunningham@cornelisnetworks.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next 0/2] Series short description
Date: Tue, 22 Aug 2023 17:31:54 +0300 [thread overview]
Message-ID: <169271471400.43535.1833309467078306989.b4-ty@kernel.org> (raw)
In-Reply-To: <169271289743.1855761.7584504317823143869.stgit@awfm-02.cornelisnetworks.com>
On Tue, 22 Aug 2023 10:07:47 -0400, Dennis Dalessandro wrote:
> Much scaled down version of Brendan's previous patches. This doesn't touch uAPI
> just refactors some code.
>
> Small fixup from Doug.
>
> Would have sent a couple weeks ago but had been dealing with the isert
> regression. Reverting that give us a clean bill of health. If too late
> for 6.6 can wait another cycle even.
>
> [...]
Applied, thanks!
[1/2] RDMA/hfi1: Move user SDMA system memory pinning code to its own file
https://git.kernel.org/rdma/rdma/c/d2c02346345337
[2/2] IB/hfi1: Reduce printing of errors during driver shut down
https://git.kernel.org/rdma/rdma/c/f5acc36b0714b7
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2023-08-22 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 14:07 [PATCH for-next 0/2] Series short description Dennis Dalessandro
2023-08-22 14:07 ` [PATCH for-next 1/2] RDMA/hfi1: Move user SDMA system memory pinning code to its own file Dennis Dalessandro
2023-08-22 14:07 ` [PATCH for-next 2/2] IB/hfi1: Reduce printing of errors during driver shut down Dennis Dalessandro
2023-08-22 14:15 ` [PATCH for-next 0/2] Series short description Dennis Dalessandro
2023-08-22 14:30 ` Leon Romanovsky
2023-08-22 14:31 ` Leon Romanovsky [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=169271471400.43535.1833309467078306989.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=bcunningham@cornelisnetworks.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=doug.miller@cornelisnetworks.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=pat.kelsey@cornelisnetworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox