All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Devesh Sharma <devesh.sharma@broadcom.com>
Cc: linux-rdma@vger.kernel.org, jgg@mellanox.com, dledford@redhat.com
Subject: Re: [PATCH for-next 0/2]: Broadcom's driver update
Date: Tue, 26 May 2020 09:03:52 +0300	[thread overview]
Message-ID: <20200526060352.GR10591@unreal> (raw)
In-Reply-To: <1590470402-32590-1-git-send-email-devesh.sharma@broadcom.com>

On Tue, May 26, 2020 at 01:20:00AM -0400, Devesh Sharma wrote:
> This series is mainly focused on adding driver fast path
> changes to support variable sized wqe support. There are
> two patches.
>
> The first patch is a big patch and contain core changes to
> support the feature. Since the change is related to fast
> path, the patch is not splitted into multiple patches.
> We want to push all related changes in one go.

It doesn't sound like a solid justification for the huge patch.
All patches in series are applied together, why is it different
for this specific feature?

Thanks

  parent reply	other threads:[~2020-05-26  6:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  5:20 [PATCH for-next 0/2]: Broadcom's driver update Devesh Sharma
2020-05-26  5:20 ` [PATCH for-next 1/2] RDMA/bnxt_re: change sq and rq to be indexed with 16B stride Devesh Sharma
2020-05-26  5:20 ` [PATCH for-next 2/2] RDMA/bnxt_re: update ABI to pass wqe-mode to user space Devesh Sharma
2020-05-26  6:03 ` Leon Romanovsky [this message]
2020-05-26 19:31 ` [PATCH for-next 0/2]: Broadcom's driver update Jason Gunthorpe
2020-05-27  5:36   ` Devesh Sharma

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=20200526060352.GR10591@unreal \
    --to=leon@kernel.org \
    --cc=devesh.sharma@broadcom.com \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --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.