From: "Gabriel L. Somlo" <somlo@cmu.edu>
To: Vasyl Gomonovych <gomonovych@gmail.com>
Cc: mst@redhat.com, qemu-devel@nongnu.org, linux-kernel@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] firmware: Use PTR_ERR_OR_ZERO()
Date: Wed, 29 Nov 2017 10:01:05 -0500 [thread overview]
Message-ID: <20171129150105.GK5774@hedwig.ini.cmu.edu> (raw)
In-Reply-To: <1511905227-30292-1-git-send-email-gomonovych@gmail.com>
Acked-by: Gabriel Somlo <somlo@cmu.edu>
On Tue, Nov 28, 2017 at 10:40:27PM +0100, Vasyl Gomonovych wrote:
> Fix ptr_ret.cocci warnings:
> drivers/firmware/efi/efi.c:610:8-14: 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
>
> Signed-off-by: Vasyl Gomonovych <gomonovych@gmail.com>
> ---
> drivers/firmware/qemu_fw_cfg.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/firmware/qemu_fw_cfg.c b/drivers/firmware/qemu_fw_cfg.c
> index 5cfe39f7a45f..18489b6a696d 100644
> --- a/drivers/firmware/qemu_fw_cfg.c
> +++ b/drivers/firmware/qemu_fw_cfg.c
> @@ -693,10 +693,8 @@ static int fw_cfg_cmdline_set(const char *arg, const struct kernel_param *kp)
> */
> fw_cfg_cmdline_dev = platform_device_register_simple("fw_cfg",
> PLATFORM_DEVID_NONE, res, processed);
> - if (IS_ERR(fw_cfg_cmdline_dev))
> - return PTR_ERR(fw_cfg_cmdline_dev);
>
> - return 0;
> + return PTR_ERR_OR_ZERO(fw_cfg_cmdline_dev);
> }
>
> static int fw_cfg_cmdline_get(char *buf, const struct kernel_param *kp)
> --
> 1.9.1
>
next prev parent reply other threads:[~2017-11-29 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 21:40 [Qemu-devel] [PATCH] firmware: Use PTR_ERR_OR_ZERO() Vasyl Gomonovych
2017-11-29 15:01 ` Gabriel L. Somlo [this message]
2017-12-01 10:15 ` Stefan Hajnoczi
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=20171129150105.GK5774@hedwig.ini.cmu.edu \
--to=somlo@cmu.edu \
--cc=gomonovych@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).