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>, <dledford@redhat.com>,
	<leonro@nvidia.com>, <sagi@grimberg.me>, <oren@nvidia.com>,
	<nitzanc@nvidia.com>, <sergeygo@nvidia.com>,
	<ngottlieb@nvidia.com>
Subject: Re: [PATCH 0/4] IB/iser cleanups and fixes for 5.11
Date: Tue, 19 Jan 2021 20:10:35 -0400	[thread overview]
Message-ID: <20210120001035.GA944141@nvidia.com> (raw)
In-Reply-To: <20210111145754.56727-1-mgurtovoy@nvidia.com>

On Mon, Jan 11, 2021 at 02:57:50PM +0000, Max Gurtovoy wrote:
> Hi Jason/Leon/Sagi,
> This series introduce some minor code conventions cleanups and 1 module
> param fix that can cause the driver to fail in connection establishment
> (if one will set max_sectors = 0).
> 
> Please consider this for the next 5.11 PR or for 5.12 merge window.
> 
> Max Gurtovoy (4):
>   IB/iser: remove unneeded semicolons
>   IB/iser: protect iscsi_max_lun module param using callback
>   IB/iser: enforce iser_max_sectors to be greater than 0
>   IB/iser: simplify prot_caps setting

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2021-01-20  0:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 14:57 [PATCH 0/4] IB/iser cleanups and fixes for 5.11 Max Gurtovoy
2021-01-11 14:57 ` [PATCH 1/4] IB/iser: remove unneeded semicolons Max Gurtovoy
2021-01-14  0:00   ` Sagi Grimberg
2021-01-11 14:57 ` [PATCH 2/4] IB/iser: protect iscsi_max_lun module param using callback Max Gurtovoy
2021-01-14  0:00   ` Sagi Grimberg
2021-01-11 14:57 ` [PATCH 3/4] IB/iser: enforce iser_max_sectors to be greater than 0 Max Gurtovoy
2021-01-14  0:02   ` Sagi Grimberg
2021-01-11 14:57 ` [PATCH 4/4] IB/iser: simplify prot_caps setting Max Gurtovoy
2021-01-14  0:03   ` Sagi Grimberg
2021-01-20  0:10 ` 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=20210120001035.GA944141@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mgurtovoy@nvidia.com \
    --cc=ngottlieb@nvidia.com \
    --cc=nitzanc@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.