All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Cheng Xu <chengyou@linux.alibaba.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org, KaiShen@linux.alibaba.com
Subject: Re: [PATCH for-next 0/4] RDMA/erdma: cleanups and updates 9-9-2022
Date: Tue, 20 Sep 2022 14:33:13 +0300	[thread overview]
Message-ID: <Yymk+bDrehINfTL7@unreal> (raw)
In-Reply-To: <20220909093822.33868-1-chengyou@linux.alibaba.com>

On Fri, Sep 09, 2022 at 05:38:18PM +0800, Cheng Xu wrote:
> Hi,
> 
> This series has new updates for erdma driver:
> - #1~#3 aim at making code more clean, including eliminating unnecessary
>   castings, removing redundant include headers, and hiding hardware
>   internal opcodes.
> - #4 introcuces dynamic mtu support.
> 
> Thanks,
> Cheng Xu
> 
> Cheng Xu (4):
>   RDMA/erdma: Eliminate unnecessary casting for erdma_post_cmd_wait
>   RDMA/erdma: Remove redundant includes
>   RDMA/erdma: Make hardware internal opcodes invisible to driver

I applied these three to -next.

>   RDMA/erdma: Support dynamic mtu

This patch needs clarification.

Thanks

      parent reply	other threads:[~2022-09-20 11:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  9:38 [PATCH for-next 0/4] RDMA/erdma: cleanups and updates 9-9-2022 Cheng Xu
2022-09-09  9:38 ` [PATCH for-next 1/4] RDMA/erdma: Eliminate unnecessary casting for erdma_post_cmd_wait Cheng Xu
2022-09-09  9:38 ` [PATCH for-next 2/4] RDMA/erdma: Remove redundant includes Cheng Xu
2022-09-09  9:38 ` [PATCH for-next 3/4] RDMA/erdma: Make hardware internal opcodes invisible to driver Cheng Xu
2022-09-09  9:38 ` [PATCH for-next 4/4] RDMA/erdma: Support dynamic mtu Cheng Xu
2022-09-20 11:32   ` Leon Romanovsky
2022-09-21  2:28     ` Cheng Xu
2022-09-21  7:35       ` Leon Romanovsky
2022-09-21  7:32   ` (subset) " Leon Romanovsky
2022-09-20 11:33 ` Leon Romanovsky [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=Yymk+bDrehINfTL7@unreal \
    --to=leon@kernel.org \
    --cc=KaiShen@linux.alibaba.com \
    --cc=chengyou@linux.alibaba.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.