From: Bob Pearson <rpearsonhpe@gmail.com>
To: jgg@nvidia.com, zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org
Cc: Bob Pearson <rpearson@hpe.com>
Subject: [PATCH for-next v2 0/6] RDMA/rxe: Misc rxe_pool cleanups
Date: Fri, 22 Jan 2021 13:29:37 -0600 [thread overview]
Message-ID: <20210122192943.5538-1-rpearson@hpe.com> (raw)
This series of patches corrects a bug introduced in rxe_pool.c
by a recent commit and then addresses several issues raised
during discussion of the bug and the proposed fix.
The first patch fixes a real bug but the other five are
stylistic and cleanup changes.
Signed-off-by: Bob Pearson <rpearson@hpe.com>
Bob Pearson (6):
RDMA/rxe: Fix bug in rxe_alloc
RDMA/rxe: Fix misleading comments and names
RDMA/rxe: Remove RXE_POOL_ATOMIC
RDMA/rxe: Remove references to ib_device and pool
RDMA/rxe: Remove unneeded pool->state
RDMA/rxe: Replace missing rxe_pool_get_index__
drivers/infiniband/sw/rxe/rxe_mcast.c | 8 +-
drivers/infiniband/sw/rxe/rxe_pool.c | 132 +++++++++-----------------
drivers/infiniband/sw/rxe/rxe_pool.h | 57 ++++++-----
3 files changed, 76 insertions(+), 121 deletions(-)
--
2.27.0
next reply other threads:[~2021-01-22 23:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 19:29 Bob Pearson [this message]
2021-01-22 19:29 ` [PATCH for-next v2 1/6] RDMA/rxe: Fix bug in rxe_alloc Bob Pearson
2021-01-22 19:29 ` [PATCH for-next v2 2/6] RDMA/rxe: Fix misleading comments and names Bob Pearson
2021-01-22 19:29 ` [PATCH for-next v2 3/6] RDMA/rxe: Remove RXE_POOL_ATOMIC Bob Pearson
2021-01-22 19:29 ` [PATCH for-next v2 4/6] RDMA/rxe: Remove references to ib_device and pool Bob Pearson
2021-01-23 1:56 ` Zhu Yanjun
2021-01-22 19:29 ` [PATCH for-next v2 5/6] RDMA/rxe: Remove unneeded pool->state Bob Pearson
2021-01-23 1:47 ` Zhu Yanjun
2021-01-22 19:29 ` [PATCH for-next v2 6/6] RDMA/rxe: Replace missing rxe_pool_get_index__ Bob Pearson
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=20210122192943.5538-1-rpearson@hpe.com \
--to=rpearsonhpe@gmail.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearson@hpe.com \
--cc=zyjzyj2000@gmail.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