From: Jason Gunthorpe <jgg@ziepe.ca>
To: Kamal Heib <kamalheib1@gmail.com>
Cc: linux-rdma@vger.kernel.org, Doug Ledford <dledford@redhat.com>,
Lijun Ou <oulijun@huawei.com>,
Selvin Xavier <selvin.xavier@broadcom.com>,
Michal Kalderon <mkalderon@marvell.com>
Subject: Re: [for-next v4 0/4] RDMA: modify_port improvements
Date: Wed, 6 Nov 2019 13:35:21 -0400 [thread overview]
Message-ID: <20191106173521.GA7971@ziepe.ca> (raw)
In-Reply-To: <20191028155931.1114-1-kamalheib1@gmail.com>
On Mon, Oct 28, 2019 at 05:59:27PM +0200, Kamal Heib wrote:
> Changelog:
> v4: Allow only IB_PORT_CM_SUP fake manipulation for RoCE providers.
> v3: Improve [patch 1/4].
> v2: Include fixes lines.
>
> This series includes three patches which fix the return values from
> modify_port() callbacks when they aren't supported.
>
> Kamal Heib (4):
> RDMA/core: Fix return code when modify_port isn't supported
> RDMA/hns: Remove unsupported modify_port callback
> RDMA/ocrdma: Remove unsupported modify_port callback
> RDMA/qedr: Remove unsupported modify_port callback
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2019-11-06 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 15:59 [for-next v4 0/4] RDMA: modify_port improvements Kamal Heib
2019-10-28 15:59 ` [for-next v4 1/4] RDMA/core: Fix return code when modify_port isn't supported Kamal Heib
2019-10-28 15:59 ` [for-next v4 2/4] RDMA/hns: Remove unsupported modify_port callback Kamal Heib
2019-10-28 15:59 ` [for-next v4 3/4] RDMA/ocrdma: " Kamal Heib
2019-10-28 15:59 ` [for-next v4 4/4] RDMA/qedr: " Kamal Heib
2019-11-06 17:35 ` 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=20191106173521.GA7971@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=kamalheib1@gmail.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mkalderon@marvell.com \
--cc=oulijun@huawei.com \
--cc=selvin.xavier@broadcom.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;
as well as URLs for NNTP newsgroup(s).