From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next v2 0/9] RDMA/rxe: Various fixes
Date: Thu, 30 Jun 2022 21:20:30 -0300 [thread overview]
Message-ID: <20220701002030.GA1088701@nvidia.com> (raw)
In-Reply-To: <20220630190425.2251-1-rpearsonhpe@gmail.com>
On Thu, Jun 30, 2022 at 02:04:17PM -0500, Bob Pearson wrote:
> Bob Pearson (9):
> RDMA/rxe: Convert pr_warn/err to pr_debug in pyverbs
> RDMA/rxe: Remove unnecessary include statement
These two are trivial, I'm going to take them right now
Thanks,
Jason
next prev parent reply other threads:[~2022-07-01 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 19:04 [PATCH for-next v2 0/9] RDMA/rxe: Various fixes Bob Pearson
2022-06-30 19:04 ` [PATCH for-next v2 1/9] RDMA/rxe: Add rxe_is_fenced() subroutine Bob Pearson
2022-07-18 2:13 ` lizhijian
2022-06-30 19:04 ` [PATCH for-next v2 2/9] RDMA/rxe: Convert pr_warn/err to pr_debug in pyverbs Bob Pearson
2022-06-30 19:04 ` [PATCH for-next v2 3/9] RDMA/rxe: Remove unnecessary include statement Bob Pearson
2022-06-30 19:04 ` [PATCH for-next v2 4/9] RDMA/rxe: Replace " Bob Pearson
2022-06-30 19:04 ` [PATCH for-next v2 5/9] RDMA/rxe: Fix rnr retry behavior Bob Pearson
2022-06-30 19:04 ` [PATCH for-next v2 6/9] RDMA/rxe: Fix deadlock in rxe_do_local_ops() Bob Pearson
2022-06-30 19:04 ` [PATCH for-next v2 7/9] RDMA/rxe: Make the tasklet exits the same Bob Pearson
2022-06-30 19:04 ` [PATCH for-next v2 8/9] RDMA/rxe: Limit the number of calls to each tasklet Bob Pearson
2022-06-30 19:04 ` [PATCH for-next v2 9/9] RDMA/rxe: Replace __rxe_do_task by rxe_run_task Bob Pearson
2022-07-01 1:24 ` lizhijian
2022-07-01 0:20 ` Jason Gunthorpe [this message]
2022-07-22 21:14 ` [PATCH for-next v2 0/9] RDMA/rxe: Various fixes Jason Gunthorpe
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=20220701002030.GA1088701@nvidia.com \
--to=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.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 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.