From: Leon Romanovsky <leonro@nvidia.com>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: <jgg@nvidia.com>,
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:30:37 +0300 [thread overview]
Message-ID: <20230822143037.GK6029@unreal> (raw)
In-Reply-To: <d2797632-439b-8d2c-e220-e8cf2bff8051@cornelisnetworks.com>
On Tue, Aug 22, 2023 at 10:15:37AM -0400, Dennis Dalessandro wrote:
> On 8/22/23 10:07 AM, 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.
> >
> > ---
> >
> > Brendan Cunningham (1):
> > RDMA/hfi1: Move user SDMA system memory pinning code to its own file
> >
> > Douglas Miller (1):
> > IB/hfi1: Reduce printing of errors during driver shut down
> >
> >
> > drivers/infiniband/hw/hfi1/Makefile | 1 +
> > drivers/infiniband/hw/hfi1/chip.c | 8 +-
> > drivers/infiniband/hw/hfi1/hfi.h | 4 +-
> > drivers/infiniband/hw/hfi1/pin_system.c | 474 ++++++++++++++++++++++++
> > drivers/infiniband/hw/hfi1/pinning.h | 20 +
> > drivers/infiniband/hw/hfi1/user_sdma.c | 441 +---------------------
> > drivers/infiniband/hw/hfi1/user_sdma.h | 17 +-
> > 7 files changed, 510 insertions(+), 455 deletions(-)
> > create mode 100644 drivers/infiniband/hw/hfi1/pin_system.c
> > create mode 100644 drivers/infiniband/hw/hfi1/pinning.h
> >
> > --
> > -Denny
> >
>
> My bad on the subject line here. Should be obvious what it's for though, small
> fix and a refactor patch for hfi1.
No worries, I rely on submitter name more than on subject line :).
Thanks
>
> -Denny
next prev parent reply other threads:[~2023-08-22 14:31 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 [this message]
2023-08-22 14:31 ` 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=20230822143037.GK6029@unreal \
--to=leonro@nvidia.com \
--cc=bcunningham@cornelisnetworks.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=doug.miller@cornelisnetworks.com \
--cc=jgg@nvidia.com \
--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