From: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
To: "Daisuke Matsuda (Fujitsu)" <matsuda-daisuke@fujitsu.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: "zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"leon@kernel.org" <leon@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>
Subject: Re: [PATCH 1/2] RDMA/rxe: add missing newline to rxe_set_mtu message
Date: Wed, 23 Aug 2023 03:04:52 +0000 [thread overview]
Message-ID: <07507497-afad-d39b-8514-11651283dd51@fujitsu.com> (raw)
In-Reply-To: <OS7PR01MB11804CAF2115EA88678B1B2AEE51CA@OS7PR01MB11804.jpnprd01.prod.outlook.com>
Daisuke
Thanks for your reviewing, beside this place, i just noticed that
there are so many places missing newline in rxe driver
except rxe_err() rxe_info() rxe_dbg() already auto added newline in the macros,
other macros should append newline by hand when being used.
A roughly count:
# git grep -n -e rxe_info -e rxe_err -e rxe_dbg | grep -v '#define' | grep -v '\\n' | wc -l
146
i will do a big cleanup for all of them later.
Thanks
Zhijian
On 23/08/2023 10:43, Matsuda, Daisuke/松田 大輔 wrote:
> On Wed, Aug 23, 2023 11:13 AM Li Zhijian wrote:
>>
>> A newline help flushing message out.
>>
>> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
>> ---
>> drivers/infiniband/sw/rxe/rxe.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/infiniband/sw/rxe/rxe.c b/drivers/infiniband/sw/rxe/rxe.c
>> index 54c723a6edda..cb2c0d54aae1 100644
>> --- a/drivers/infiniband/sw/rxe/rxe.c
>> +++ b/drivers/infiniband/sw/rxe/rxe.c
>> @@ -161,7 +161,7 @@ void rxe_set_mtu(struct rxe_dev *rxe, unsigned int ndev_mtu)
>> port->attr.active_mtu = mtu;
>> port->mtu_cap = ib_mtu_enum_to_int(mtu);
>>
>> - rxe_info_dev(rxe, "Set mtu to %d", port->mtu_cap);
>> + rxe_info_dev(rxe, "Set mtu to %d\n", port->mtu_cap);
>> }
>>
>> /* called by ifc layer to create new rxe device.
>> --
>> 2.29.2
>
> Reviewed-by: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>
>
next prev parent reply other threads:[~2023-08-23 3:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 2:13 Li Zhijian
2023-08-23 2:13 ` [PATCH 2/2] RDMA/rxe: Call rxe_set_mtu after rxe_register_device Li Zhijian
2023-08-23 2:46 ` Daisuke Matsuda (Fujitsu)
2023-08-23 2:43 ` [PATCH 1/2] RDMA/rxe: add missing newline to rxe_set_mtu message Daisuke Matsuda (Fujitsu)
2023-08-23 3:04 ` Zhijian Li (Fujitsu) [this message]
2023-08-23 5:10 ` Daisuke Matsuda (Fujitsu)
2023-08-23 6:12 ` Zhu Yanjun
2023-08-23 6:25 ` Zhijian Li (Fujitsu)
2023-08-23 6:35 ` Zhu Yanjun
2023-08-23 6:47 ` Zhijian Li (Fujitsu)
2023-08-23 6:59 ` Zhu Yanjun
2023-08-23 7:20 ` Zhijian Li (Fujitsu)
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=07507497-afad-d39b-8514-11651283dd51@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matsuda-daisuke@fujitsu.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
all inboxes | Powered by JetHome®