All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: linux-rdma@vger.kernel.org, sagi@grimberg.me, oren@nvidia.com,
	sergeygo@nvidia.com, israelr@nvidia.com, leonro@nvidia.com
Subject: Re: [PATCH v2 0/4] iSER cleanups and fixes for 5.18
Date: Fri, 18 Mar 2022 15:19:48 -0300	[thread overview]
Message-ID: <20220318181948.GA659567@nvidia.com> (raw)
In-Reply-To: <20220308145546.8372-1-mgurtovoy@nvidia.com>

On Tue, Mar 08, 2022 at 04:55:42PM +0200, Max Gurtovoy wrote:
> Max Gurtovoy (4):
>   IB/iser: remove iser_reg_data_sg helper function
>   IB/iser: use iser_fr_desc as registration context
>   IB/iser: generalize map/unmap dma tasks
>   IB/iser: fix error flow in case of registration failure

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2022-03-18 18:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 14:55 [PATCH v2 0/4] iSER cleanups and fixes for 5.18 Max Gurtovoy
2022-03-08 14:55 ` [PATCH v2 1/4] IB/iser: remove iser_reg_data_sg helper function Max Gurtovoy
2022-03-16 15:06   ` Sagi Grimberg
2022-03-08 14:55 ` [PATCH v2 2/4] IB/iser: use iser_fr_desc as registration context Max Gurtovoy
2022-03-16 15:09   ` Sagi Grimberg
2022-03-08 14:55 ` [PATCH v2 3/4] IB/iser: generalize map/unmap dma tasks Max Gurtovoy
2022-03-16 15:13   ` Sagi Grimberg
2022-03-08 14:55 ` [PATCH v2 4/4] IB/iser: fix error flow in case of registration failure Max Gurtovoy
2022-03-16 15:14   ` Sagi Grimberg
2022-03-16 16:02     ` Max Gurtovoy
2022-03-17  7:31       ` Sagi Grimberg
2022-03-18 18:19 ` Jason Gunthorpe [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=20220318181948.GA659567@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=israelr@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mgurtovoy@nvidia.com \
    --cc=oren@nvidia.com \
    --cc=sagi@grimberg.me \
    --cc=sergeygo@nvidia.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 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.