From: Thierry Reding <thierry.reding@gmail.com>
To: zhengbin <zhengbin13@huawei.com>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
jonathanh@nvidia.com, linux-tegra@vger.kernel.org,
treding@nvidia.com
Subject: Re: [PATCH 0/2] drm/tegra: Use PTR_ERR_OR_ZERO() to simplify code
Date: Mon, 18 Nov 2019 14:23:57 +0100 [thread overview]
Message-ID: <20191118132357.GC2246533@ulmo> (raw)
In-Reply-To: <1574077572-59152-1-git-send-email-zhengbin13@huawei.com>
[-- Attachment #1.1: Type: text/plain, Size: 506 bytes --]
On Mon, Nov 18, 2019 at 07:46:10PM +0800, zhengbin wrote:
> zhengbin (2):
> drm/tegra: Use PTR_ERR_OR_ZERO() to simplify code in
> tegra_bo_dumb_create
> drm/tegra: Use PTR_ERR_OR_ZERO() to simplify code in tegra_gem_create
>
> drivers/gpu/drm/tegra/drm.c | 5 +----
> drivers/gpu/drm/tegra/gem.c | 5 +----
> 2 files changed, 2 insertions(+), 8 deletions(-)
As I explained in response to the same patches sent for other drivers
already, I don't think this has any merit.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-18 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 11:46 [PATCH 0/2] drm/tegra: Use PTR_ERR_OR_ZERO() to simplify code zhengbin
2019-11-18 11:46 ` [PATCH 1/2] drm/tegra: Use PTR_ERR_OR_ZERO() to simplify code in tegra_bo_dumb_create zhengbin
2019-11-18 11:46 ` [PATCH 2/2] drm/tegra: Use PTR_ERR_OR_ZERO() to simplify code in tegra_gem_create zhengbin
2019-11-18 13:23 ` Thierry Reding [this message]
2019-11-19 11:44 ` [PATCH 0/2] drm/tegra: Use PTR_ERR_OR_ZERO() to simplify code Jani Nikula
2019-11-19 11:52 ` Jani Nikula
2019-11-19 12:40 ` Julia Lawall
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=20191118132357.GC2246533@ulmo \
--to=thierry.reding@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.com \
--cc=zhengbin13@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;
as well as URLs for NNTP newsgroup(s).