All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gomonovych, Vasyl" <gomonovych@gmail.com>
To: Christoffer Dall <cdall@linaro.org>
Cc: Christoffer Dall <christoffer.dall@linaro.org>,
	marc.zyngier@arm.com, eric.auger@redhat.com,
	andre.przywara@arm.com, wanghaibin.wang@huawei.com,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: arm: Use PTR_ERR_OR_ZERO()
Date: Mon, 4 Dec 2017 12:11:22 +0100	[thread overview]
Message-ID: <CAHYXAnL3DVkDMF03QRV62RCFzmViDGYR2rQHBS44jyCo2FRgqw@mail.gmail.com> (raw)
In-Reply-To: <20171201080049.GB4218@cbox>

Hi Christoffer

It is just syntax sugar of course
and in mentioned function context it looks harmonically because it is
in the end of function return statement.
But in context of around source files it is looks not so harmonically because
existing code uses old approach.
And this old approach is only in one place here.
So it is just a try to fix the warning and may be force to use it in a
future changes.

Regards Vasyl

On Fri, Dec 1, 2017 at 9:00 AM, Christoffer Dall <cdall@linaro.org> wrote:
> Hi Vasyl,
>
> On Tue, Nov 28, 2017 at 11:48:17PM +0100, Vasyl Gomonovych wrote:
>> Fix ptr_ret.cocci warnings:
>> virt/kvm/arm/vgic/vgic-its.c:971:1-3: WARNING: PTR_ERR_OR_ZERO can be used
>>
>> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>>
>> Generated by: scripts/coccinelle/api/ptr_ret.cocci
>
> For new code, sure it would make sense to use this.
>
> But why is it worth changing existing code to use PTR_ERR_OR_ZERO?
>
> Thanks,
> -Christoffer
>
>>
>> Signed-off-by: Vasyl Gomonovych <gomonovych@gmail.com>
>> ---
>>  virt/kvm/arm/vgic/vgic-its.c | 4 +---
>>  1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/virt/kvm/arm/vgic/vgic-its.c b/virt/kvm/arm/vgic/vgic-its.c
>> index 1f761a9991e7..28d85754320b 100644
>> --- a/virt/kvm/arm/vgic/vgic-its.c
>> +++ b/virt/kvm/arm/vgic/vgic-its.c
>> @@ -1032,10 +1032,8 @@ static int vgic_its_cmd_handle_mapd(struct kvm *kvm, struct vgic_its *its,
>>
>>       device = vgic_its_alloc_device(its, device_id, itt_addr,
>>                                      num_eventid_bits);
>> -     if (IS_ERR(device))
>> -             return PTR_ERR(device);
>>
>> -     return 0;
>> +     return PTR_ERR_OR_ZERO(device);
>>  }
>>
>>  /*
>> --
>> 1.9.1
>>



-- 
Доброї вам пори дня.

WARNING: multiple messages have this Message-ID (diff)
From: gomonovych@gmail.com (Gomonovych, Vasyl)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm: Use PTR_ERR_OR_ZERO()
Date: Mon, 4 Dec 2017 12:11:22 +0100	[thread overview]
Message-ID: <CAHYXAnL3DVkDMF03QRV62RCFzmViDGYR2rQHBS44jyCo2FRgqw@mail.gmail.com> (raw)
In-Reply-To: <20171201080049.GB4218@cbox>

Hi Christoffer

It is just syntax sugar of course
and in mentioned function context it looks harmonically because it is
in the end of function return statement.
But in context of around source files it is looks not so harmonically because
existing code uses old approach.
And this old approach is only in one place here.
So it is just a try to fix the warning and may be force to use it in a
future changes.

Regards Vasyl

On Fri, Dec 1, 2017 at 9:00 AM, Christoffer Dall <cdall@linaro.org> wrote:
> Hi Vasyl,
>
> On Tue, Nov 28, 2017 at 11:48:17PM +0100, Vasyl Gomonovych wrote:
>> Fix ptr_ret.cocci warnings:
>> virt/kvm/arm/vgic/vgic-its.c:971:1-3: WARNING: PTR_ERR_OR_ZERO can be used
>>
>> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>>
>> Generated by: scripts/coccinelle/api/ptr_ret.cocci
>
> For new code, sure it would make sense to use this.
>
> But why is it worth changing existing code to use PTR_ERR_OR_ZERO?
>
> Thanks,
> -Christoffer
>
>>
>> Signed-off-by: Vasyl Gomonovych <gomonovych@gmail.com>
>> ---
>>  virt/kvm/arm/vgic/vgic-its.c | 4 +---
>>  1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/virt/kvm/arm/vgic/vgic-its.c b/virt/kvm/arm/vgic/vgic-its.c
>> index 1f761a9991e7..28d85754320b 100644
>> --- a/virt/kvm/arm/vgic/vgic-its.c
>> +++ b/virt/kvm/arm/vgic/vgic-its.c
>> @@ -1032,10 +1032,8 @@ static int vgic_its_cmd_handle_mapd(struct kvm *kvm, struct vgic_its *its,
>>
>>       device = vgic_its_alloc_device(its, device_id, itt_addr,
>>                                      num_eventid_bits);
>> -     if (IS_ERR(device))
>> -             return PTR_ERR(device);
>>
>> -     return 0;
>> +     return PTR_ERR_OR_ZERO(device);
>>  }
>>
>>  /*
>> --
>> 1.9.1
>>



-- 
?????? ??? ???? ???.

  reply	other threads:[~2017-12-04 11:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 22:48 [PATCH] KVM: arm: Use PTR_ERR_OR_ZERO() Vasyl Gomonovych
2017-11-28 22:48 ` Vasyl Gomonovych
2017-12-01  8:00 ` Christoffer Dall
2017-12-01  8:00   ` Christoffer Dall
2017-12-01  8:00   ` Christoffer Dall
2017-12-04 11:11   ` Gomonovych, Vasyl [this message]
2017-12-04 11:11     ` Gomonovych, Vasyl
2017-12-04 19:40     ` Christoffer Dall
2017-12-04 19:40       ` Christoffer Dall

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=CAHYXAnL3DVkDMF03QRV62RCFzmViDGYR2rQHBS44jyCo2FRgqw@mail.gmail.com \
    --to=gomonovych@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=cdall@linaro.org \
    --cc=christoffer.dall@linaro.org \
    --cc=eric.auger@redhat.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=wanghaibin.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.