Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
To: "Pearson, Robert B" <robert.pearson2@hpe.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: "leon@kernel.org" <leon@kernel.org>,
	"jgg@ziepe.ca" <jgg@ziepe.ca>,
	"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>,
	"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>
Subject: Re: [PATCH 2/2] RDMA/rxe: Rename rxe_atomic_reply to atomic_reply
Date: Wed, 6 Jul 2022 12:14:25 +0000	[thread overview]
Message-ID: <1e81e77d-f5d4-3f23-49fc-9e147dd68d46@fujitsu.com> (raw)
In-Reply-To: <MW4PR84MB23075C8A422D7C87C5F0C4B7BC809@MW4PR84MB2307.NAMPRD84.PROD.OUTLOOK.COM>

On 2022/7/6 15:38, Pearson, Robert B wrote:
> Generally over time I have been adding a rxe_ prefix to all searchable names static or non static.
> This avoids collisions with similar names in other drivers with e.g. ctags. I agree a unified naming
> Scheme is good but would like to see one with a common prefix for subroutine names.
Hi Bob,

I think it's hard to use unique name in all drivers. I saw that all 
functions called by different qp states don't use the rxe_ prefix in 
rxe_responders so just remove the rxe_ prefix. We can drop the patch if 
you don't agree with this change.

Best Regards,
Xiao Yang
> 
> Bob
> 
> -----Original Message-----
> From: Xiao Yang <yangx.jy@fujitsu.com>
> Sent: Tuesday, July 5, 2022 6:46 AM
> To: linux-rdma@vger.kernel.org
> Cc: leon@kernel.org; jgg@ziepe.ca; rpearsonhpe@gmail.com; zyjzyj2000@gmail.com; Xiao Yang <yangx.jy@fujitsu.com>
> Subject: [PATCH 2/2] RDMA/rxe: Rename rxe_atomic_reply to atomic_reply
> 
> It's better to use the unified naming format.
> 
> Signed-off-by: Xiao Yang <yangx.jy@fujitsu.com>
> ---
>   drivers/infiniband/sw/rxe/rxe_resp.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/infiniband/sw/rxe/rxe_resp.c b/drivers/infiniband/sw/rxe/rxe_resp.c
> index 5536582b8fe4..265e46fe050f 100644
> --- a/drivers/infiniband/sw/rxe/rxe_resp.c
> +++ b/drivers/infiniband/sw/rxe/rxe_resp.c
> @@ -595,7 +595,7 @@ static struct resp_res *rxe_prepare_res(struct rxe_qp *qp,
>   /* Guarantee atomicity of atomic operations at the machine level. */  static DEFINE_SPINLOCK(atomic_ops_lock);
>   
> -static enum resp_states rxe_atomic_reply(struct rxe_qp *qp,
> +static enum resp_states atomic_reply(struct rxe_qp *qp,
>   					 struct rxe_pkt_info *pkt)
>   {
>   	u64 *vaddr;
> @@ -1333,7 +1333,7 @@ int rxe_responder(void *arg)
>   			state = read_reply(qp, pkt);
>   			break;
>   		case RESPST_ATOMIC_REPLY:
> -			state = rxe_atomic_reply(qp, pkt);
> +			state = atomic_reply(qp, pkt);
>   			break;
>   		case RESPST_ACKNOWLEDGE:
>   			state = acknowledge(qp, pkt);
> --
> 2.34.1
> 
> 
> 

  reply	other threads:[~2022-07-06 12:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 11:46 [PATCH 1/2] RDMA/rxe: Add common rxe_prepare_res() Xiao Yang
2022-07-05 11:46 ` [PATCH 2/2] RDMA/rxe: Rename rxe_atomic_reply to atomic_reply Xiao Yang
2022-07-06  7:38   ` Pearson, Robert B
2022-07-06 12:14     ` yangx.jy [this message]
2022-07-14 17:05       ` Bob Pearson
2022-07-05 13:58 ` [PATCH 1/2] RDMA/rxe: Add common rxe_prepare_res() 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=1e81e77d-f5d4-3f23-49fc-9e147dd68d46@fujitsu.com \
    --to=yangx.jy@fujitsu.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=robert.pearson2@hpe.com \
    --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