From: Leon Romanovsky <leonro@nvidia.com>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: Alistair Popple <apopple@nvidia.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"jgg@nvidia.com" <jgg@nvidia.com>
Subject: Re: Re: [PATCH] RDMA/siw: Fix user page pinning accounting
Date: Sun, 5 Feb 2023 15:05:52 +0200 [thread overview]
Message-ID: <Y9+psKn6GrceGeG3@unreal> (raw)
In-Reply-To: <SA0PR15MB3919BA817A04C53AEC8B66FA99D69@SA0PR15MB3919.namprd15.prod.outlook.com>
On Thu, Feb 02, 2023 at 09:04:06AM +0000, Bernard Metzler wrote:
>
>
> > -----Original Message-----
> > From: Alistair Popple <apopple@nvidia.com>
> > Sent: Thursday, 2 February 2023 08:44
> > To: Bernard Metzler <BMT@zurich.ibm.com>
> > Cc: linux-rdma@vger.kernel.org; jgg@nvidia.com; leonro@nvidia.com
> > Subject: [EXTERNAL] Re: [PATCH] RDMA/siw: Fix user page pinning
> > accounting
> >
> >
> > Thanks for cleaning this up, will make any potential follow on I do
> > much easier. Feel free to add:
> >
> > Reviewed-by: Alistair Popple <apopple@nvidia.com>
> >
>
> Thanks a lot! I'll resend for the last time (I hope), having you
> as a reviewer.
You don't need to resend for this. Patchworks catches all *-by tags and
allows us to add them automatically.
However, it will be great if you write target rdma-next/rdma-rc in
subject of the patch.
Thanks
>
> Many thanks,
> Bernard.
>
next prev parent reply other threads:[~2023-02-05 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 11:55 [PATCH] RDMA/siw: Fix user page pinning accounting Bernard Metzler
2023-02-02 7:44 ` Alistair Popple
2023-02-02 9:04 ` Bernard Metzler
2023-02-05 13:05 ` Leon Romanovsky [this message]
2023-02-06 13:21 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2023-01-30 13:32 Bernard Metzler
2023-01-31 0:09 ` Alistair Popple
2023-01-31 11:05 ` Bernard Metzler
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=Y9+psKn6GrceGeG3@unreal \
--to=leonro@nvidia.com \
--cc=BMT@zurich.ibm.com \
--cc=apopple@nvidia.com \
--cc=jgg@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.