All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamal Heib <kamalheib1@gmail.com>
To: linux-rdma@vger.kernel.org
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Doug Ledford <dledford@redhat.com>
Subject: Re: [PATCH for-next 0/5] RDMA/providers: Set max_pkey attribute
Date: Mon, 6 Jul 2020 12:06:10 +0300	[thread overview]
Message-ID: <20200706090610.GA366031@kheib-workstation> (raw)
In-Reply-To: <20200706075419.361484-1-kamalheib1@gmail.com>

On Mon, Jul 06, 2020 at 10:54:14AM +0300, Kamal Heib wrote:
> This patch set makes sure to set the max_pkeys attribute to the providers
> that aren't setting it or not setting it correctly.
> 
> Kamal Heib (5):
>   RDMA/siw: Set max_pkeys attribute
>   RDMA/efa: Set max_pkeys attribute
>   RDMA/cxgb4: Set max_pkeys attribute
>   RDMA/i40iw: Set max_pkeys attribute
>   RDMA/usnic: Fix reported max_pkeys attribute
> 
>  drivers/infiniband/hw/cxgb4/provider.c       | 1 +
>  drivers/infiniband/hw/efa/efa_verbs.c        | 1 +
>  drivers/infiniband/hw/i40iw/i40iw_verbs.c    | 1 +
>  drivers/infiniband/hw/usnic/usnic_ib_verbs.c | 2 +-
>  drivers/infiniband/sw/siw/siw_verbs.c        | 1 +
>  5 files changed, 5 insertions(+), 1 deletion(-)
> 
> -- 
> 2.25.4
> 

Self-nack series, I'll send a v2 with the efa patch dropped and target
for-rc branch.

Nacked-by: Kamal Heib <kamalheib1@gmail.com> 

      parent reply	other threads:[~2020-07-06  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06  7:54 [PATCH for-next 0/5] RDMA/providers: Set max_pkey attribute Kamal Heib
2020-07-06  7:54 ` [PATCH for-next 1/5] RDMA/siw: Set max_pkeys attribute Kamal Heib
2020-07-06  7:54 ` [PATCH for-next 2/5] RDMA/efa: " Kamal Heib
2020-07-06  7:58   ` Gal Pressman
2020-07-06  8:16     ` Kamal Heib
2020-07-06  7:54 ` [PATCH for-next 3/5] RDMA/cxgb4: " Kamal Heib
2020-07-06  7:54 ` [PATCH for-next 4/5] RDMA/i40iw: " Kamal Heib
2020-07-06  7:54 ` [PATCH for-next 5/5] RDMA/usnic: Fix reported " Kamal Heib
2020-07-06  9:06 ` Kamal Heib [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=20200706090610.GA366031@kheib-workstation \
    --to=kamalheib1@gmail.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --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.