linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Kamal Heib <kamalheib1@gmail.com>
Cc: <linux-rdma@vger.kernel.org>, Doug Ledford <dledford@redhat.com>,
	"Zhu Yanjun" <yanjunz@mellanox.com>
Subject: Re: [PATCH for-next v1 0/4] RDMA/rxe: Cleanups and improvements
Date: Thu, 16 Jul 2020 14:01:11 -0300	[thread overview]
Message-ID: <20200716170111.GA2644423@nvidia.com> (raw)
In-Reply-To: <20200705104313.283034-1-kamalheib1@gmail.com>

On Sun, Jul 05, 2020 at 01:43:09PM +0300, Kamal Heib wrote:
> These series include few cleanup patches to the rxe driver.
> 
> V1:
> - patch #4: Fix commit message.
> 
> Kamal Heib (4):
>   RDMA/rxe: Drop pointless checks in rxe_init_ports
>   RDMA/rxe: Return void from rxe_init_port_param()
>   RDMA/rxe: Return void from rxe_mem_init_dma()
>   RDMA/rxe: Remove rxe_link_layer()

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2020-07-16 17:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05 10:43 [PATCH for-next v1 0/4] RDMA/rxe: Cleanups and improvements Kamal Heib
2020-07-05 10:43 ` [PATCH for-next v1 1/4] RDMA/rxe: Drop pointless checks in rxe_init_ports Kamal Heib
2020-07-05 13:20   ` Leon Romanovsky
2020-07-05 10:43 ` [PATCH for-next v1 2/4] RDMA/rxe: Return void from rxe_init_port_param() Kamal Heib
2020-07-05 13:20   ` Leon Romanovsky
2020-07-05 10:43 ` [PATCH for-next v1 3/4] RDMA/rxe: Return void from rxe_mem_init_dma() Kamal Heib
2020-07-05 13:20   ` Leon Romanovsky
2020-07-05 10:43 ` [PATCH for-next v1 4/4] RDMA/rxe: Remove rxe_link_layer() Kamal Heib
2020-07-05 12:59   ` Zhu Yanjun
2020-07-05 13:21   ` Leon Romanovsky
2020-07-14  8:14 ` [PATCH for-next v1 0/4] RDMA/rxe: Cleanups and improvements Kamal Heib
2020-07-14 19:56   ` Jason Gunthorpe
2020-07-15  9:48     ` Kamal Heib
2020-07-16 17:01 ` 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=20200716170111.GA2644423@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=kamalheib1@gmail.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=yanjunz@mellanox.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).