From: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
To: Markus Elfring <Markus.Elfring@web.de>,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Chen Tao <chentao107@huawei.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Drew Davenport <ddavenport@chromium.org>,
Kalyan Thota <kalyan_t@codeaurora.org>,
Rob Clark <robdclark@gmail.com>, Sam Ravnborg <sam@ravnborg.org>,
Sean Paul <sean@poorly.run>, zhengbin <zhengbin13@huawei.com>
Subject: Re: [PATCH] drm/msm/dpu: fix wrong return value in dpu_encoder_init()
Date: Fri, 3 Jul 2020 12:19:48 +0800 [thread overview]
Message-ID: <87c184ee-dfe7-03dc-e3c9-27996c57d6cd@linux.alibaba.com> (raw)
In-Reply-To: <1c338c4c-c185-0b37-eabb-1072a6502ec0@web.de>
On 2020/7/2 22:04, Markus Elfring wrote:
>> A positive value ENOMEM is returned here. I thinr this is a typo error.
>> It is necessary to return a negative error value.
>
> I imagine that a small adjustment could be nice for this change description.
>
> How do you think about to follow progress for the integration of
> a previous patch like “[RESEND] drm/msm/dpu: fix error return code in dpu_encoder_init”?
> https://lore.kernel.org/dri-devel/20200618062803.152097-1-chentao107@huawei.com/
> https://lore.kernel.org/patchwork/patch/1257957/
> https://lkml.org/lkml/2020/6/18/46
>
> Regards,
> Markus
>
This is the same fix, please ignore this patch.
Thanks,
Tianjia
next prev parent reply other threads:[~2020-07-03 4:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 14:04 [PATCH] drm/msm/dpu: fix wrong return value in dpu_encoder_init() Markus Elfring
2020-07-03 4:19 ` Tianjia Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-02 14:04 Markus Elfring
2020-07-01 4:11 Tianjia Zhang
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=87c184ee-dfe7-03dc-e3c9-27996c57d6cd@linux.alibaba.com \
--to=tianjia.zhang@linux.alibaba.com \
--cc=Markus.Elfring@web.de \
--cc=airlied@linux.ie \
--cc=chentao107@huawei.com \
--cc=daniel@ffwll.ch \
--cc=ddavenport@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=kalyan_t@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sam@ravnborg.org \
--cc=sean@poorly.run \
--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).