From: Stephen Warren <swarren@wwwdotorg.org>
To: Duan Jiong <duanj.fnst@cn.fujitsu.com>,
kernel@pengutronix.de, linux@arm.linux.org.uk,
a.zummo@towertech.it, airlied@linux.ie
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
"Thierry Reding" <treding@nvidia.com>,
"Terje Bergström" <tbergstrom@nvidia.com>
Subject: Re: [PATCH] drm/tegra: replace IS_ERR and PTR_ERR with PTR_ERR_OR_ZERO
Date: Wed, 06 Nov 2013 09:49:55 -0700 [thread overview]
Message-ID: <527A7333.9090409@wwwdotorg.org> (raw)
In-Reply-To: <1383724435-15380-1-git-send-email-duanj.fnst@cn.fujitsu.com>
On 11/06/2013 12:53 AM, Duan Jiong wrote:
> This patch fixes coccinelle error regarding usage of IS_ERR and
> PTR_ERR instead of PTR_ERR_OR_ZERO.
> diff --git a/drivers/gpu/drm/tegra/gem.c b/drivers/gpu/drm/tegra/gem.c
> @@ -199,10 +199,7 @@ int tegra_bo_dumb_create(struct drm_file *file, struct drm_device *drm,
>
> bo = tegra_bo_create_with_handle(file, drm, args->size, 0,
> &args->handle);
> - if (IS_ERR(bo))
> - return PTR_ERR(bo);
> -
> - return 0;
> + return PTR_ERR_OR_ZERO(bo);
> }
I suppose that's fine, although I wonder if it'll cause churn should we
ever need to add code to the tail end of the function.
BTW, why were all the similar patches that had nothing to do with Tegra
sent to the linux-tegra@ mailing list? You also didn't CC the
maintainers of drivers/gpu/drm/tegra/ on this patch. Plus this patch has
nothing to do with the rtc-linux@ mailing list.
next prev parent reply other threads:[~2013-11-06 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 7:53 [PATCH] drm/tegra: replace IS_ERR and PTR_ERR with PTR_ERR_OR_ZERO Duan Jiong
2013-11-06 16:49 ` Stephen Warren [this message]
[not found] ` <527A7333.9090409-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-07 1:15 ` Duan Jiong
2013-11-11 6:23 ` Thierry Reding
-- strict thread matches above, loose matches on Subject: below --
2014-04-11 8:36 Duan Jiong
[not found] ` <1397205401-24148-1-git-send-email-duanj.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-04-11 15:48 ` Stephen Warren
2014-04-16 19:49 ` Thierry Reding
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=527A7333.9090409@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=a.zummo@towertech.it \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=duanj.fnst@cn.fujitsu.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rtc-linux@googlegroups.com \
--cc=tbergstrom@nvidia.com \
--cc=treding@nvidia.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