From: Bob Pearson <rpearsonhpe@gmail.com>
To: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>,
"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>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>
Subject: Re: [PATCH 2/2] RDMA/rxe: Rename rxe_atomic_reply to atomic_reply
Date: Thu, 14 Jul 2022 12:05:40 -0500 [thread overview]
Message-ID: <c9221de5-805e-1a2f-5084-dbbe785bf80d@gmail.com> (raw)
In-Reply-To: <1e81e77d-f5d4-3f23-49fc-9e147dd68d46@fujitsu.com>
On 7/6/22 07:14, yangx.jy@fujitsu.com wrote:
> 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
I fought on your side of this argument with Zhu a while back but now I am completely on his side.
Linux has a lot of lines and generic subroutine names will very often collide all over the place.
The better answer is to add rxe_ not remove it. It's not super critical so I have been doing it as
a background task whenever I touch a piece of code. If you get the urge to make things more consistent
feel free to do that but by adding a prefix and not deleting it.
Bob
next prev parent reply other threads:[~2022-07-14 17:05 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
2022-07-14 17:05 ` Bob Pearson [this message]
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=c9221de5-805e-1a2f-5084-dbbe785bf80d@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=robert.pearson2@hpe.com \
--cc=yangx.jy@fujitsu.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