public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: liweihang <liweihang@huawei.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "dledford@redhat.com" <dledford@redhat.com>,
	"leon@kernel.org" <leon@kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	Linuxarm <linuxarm@huawei.com>,
	liangwenpeng <liangwenpeng@huawei.com>
Subject: Re: [PATCH for-next] RDMA/core: Fix incorrect print format specifier
Date: Tue, 22 Jun 2021 03:39:48 +0000	[thread overview]
Message-ID: <d4618e18227a449fa14199aa8e81fb55@huawei.com> (raw)
In-Reply-To: 20210621184054.GA2341530@nvidia.com

On 2021/6/22 2:41, Jason Gunthorpe wrote:
> On Thu, Jun 10, 2021 at 07:40:32PM +0800, Weihang Li wrote:
>> From: Wenpeng Liang <liangwenpeng@huawei.com>
>>
>> There are some '%u' for 'int' and '%d' for 'unsigend int', they should be
>> fixed.
> 
> What tool found these? Mildly surprised normal gcc doesn't complain
>  

They were found by Coverity. I'm using GCC 10.2.0, it can't find the misused
'%u' and '%d', it can only find the case of using '%s' for a integer.

Weihang

>> Signed-off-by: Wenpeng Liang <liangwenpeng@huawei.com>
>> Signed-off-by: Weihang Li <liweihang@huawei.com>
>> ---
>>  drivers/infiniband/core/cache.c       | 10 +++++-----
>>  drivers/infiniband/core/cm.c          |  2 +-
>>  drivers/infiniband/core/iwpm_msg.c    | 22 +++++++++++-----------
>>  drivers/infiniband/core/iwpm_util.c   |  4 ++--
>>  drivers/infiniband/core/mad.c         | 10 +++++-----
>>  drivers/infiniband/core/netlink.c     |  2 +-
>>  drivers/infiniband/core/rw.c          |  8 ++++----
>>  drivers/infiniband/core/security.c    |  2 +-
>>  drivers/infiniband/core/sysfs.c       | 10 +++++-----
>>  drivers/infiniband/core/ud_header.c   |  8 ++++----
>>  drivers/infiniband/core/umem_odp.c    |  2 +-
>>  drivers/infiniband/core/user_mad.c    |  4 ++--
>>  drivers/infiniband/core/uverbs_cmd.c  |  2 +-
>>  drivers/infiniband/core/uverbs_uapi.c |  2 +-
>>  drivers/infiniband/core/verbs.c       |  2 +-
>>  15 files changed, 45 insertions(+), 45 deletions(-)
> 
> Applied to for-next, thanks
> 
> Jason
> 


      reply	other threads:[~2021-06-22  3:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 11:40 [PATCH for-next] RDMA/core: Fix incorrect print format specifier Weihang Li
2021-06-21 18:40 ` Jason Gunthorpe
2021-06-22  3:39   ` liweihang [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=d4618e18227a449fa14199aa8e81fb55@huawei.com \
    --to=liweihang@huawei.com \
    --cc=dledford@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=liangwenpeng@huawei.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@huawei.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