From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: leon@kernel.org, zyjzyj2000@gmail.com, jhack@hpe.com,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next v2 00/16] Use ibdev_dbg instead of pr_xxx
Date: Thu, 10 Nov 2022 15:36:57 -0400 [thread overview]
Message-ID: <Y21S2V8Q2i66zElc@nvidia.com> (raw)
In-Reply-To: <20221103171013.20659-1-rpearsonhpe@gmail.com>
On Thu, Nov 03, 2022 at 12:09:58PM -0500, Bob Pearson wrote:
> This patch series replaces calls to pr_xxx with calls to ibdev_dbg
> using macros for rxe objects adapted from similar macros from siw,
> except in situations where the rdma device is not in scope.
>
> This patch series is based on the current for-next branch.
>
> v2:
> Fixed a typo in 01/16 in rxe_dbg_uc().
> Made fixes to 01/16 from a comment by Jason Gunthorp to enclose
> macro parameters in parentheses.
> Fixed an error in 06/16 caught by the kernel test robot <lkp@intel.com>
>
> Bob Pearson (16):
> RDMA/rxe: Add ibdev_dbg macros for rxe
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_comp.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_cq.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_mr.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_mw.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_net.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_qp.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_req.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_resp.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_srq.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_verbs.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_av.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_task.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_icrc.c
> RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_mmap.c
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2022-11-10 19:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 17:09 [PATCH for-next v2 00/16] Use ibdev_dbg instead of pr_xxx Bob Pearson
2022-11-03 17:09 ` [PATCH for-next v2 01/16] RDMA/rxe: Add ibdev_dbg macros for rxe Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 02/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_comp.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 03/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_cq.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 04/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_mr.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 05/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_mw.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 06/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_net.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 07/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_qp.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 08/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_req.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 09/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_resp.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 10/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_srq.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 11/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_verbs.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 12/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_av.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 13/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_task.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 14/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 15/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_icrc.c Bob Pearson
2022-11-03 17:10 ` [PATCH for-next v2 16/16] RDMA/rxe: Replace pr_xxx by rxe_dbg_xxx in rxe_mmap.c Bob Pearson
2022-11-10 19:36 ` 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=Y21S2V8Q2i66zElc@nvidia.com \
--to=jgg@nvidia.com \
--cc=jhack@hpe.com \
--cc=leon@kernel.org \
--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 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).