From: Shawn Guo <shawnguo@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Daniel Vetter <daniel.vetter@intel.com>
Cc: airlied@linux.ie, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: zte: Fix an error handling path in 'zx_crtc_bind()'
Date: Mon, 12 Mar 2018 07:35:26 +0000 [thread overview]
Message-ID: <20180312073524.GM3217@dragon> (raw)
In-Reply-To: <20180311223203.3669-1-christophe.jaillet@wanadoo.fr>
+ Daniel
On Sun, Mar 11, 2018 at 11:32:03PM +0100, Christophe JAILLET wrote:
> 'ret' is known to be 0 at this point. It must be updated by the value
> returned by 'clk_prepare_enable()'.
>
> Fixes: 0a886f59528a ("drm: zte: add initial vou drm driver")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Acked-by: Shawn Guo <shawnguo@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Daniel Vetter <daniel.vetter@intel.com>
Cc: airlied@linux.ie, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: zte: Fix an error handling path in 'zx_crtc_bind()'
Date: Mon, 12 Mar 2018 15:35:26 +0800 [thread overview]
Message-ID: <20180312073524.GM3217@dragon> (raw)
In-Reply-To: <20180311223203.3669-1-christophe.jaillet@wanadoo.fr>
+ Daniel
On Sun, Mar 11, 2018 at 11:32:03PM +0100, Christophe JAILLET wrote:
> 'ret' is known to be 0 at this point. It must be updated by the value
> returned by 'clk_prepare_enable()'.
>
> Fixes: 0a886f59528a ("drm: zte: add initial vou drm driver")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Acked-by: Shawn Guo <shawnguo@kernel.org>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Daniel Vetter <daniel.vetter@intel.com>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] drm: zte: Fix an error handling path in 'zx_crtc_bind()'
Date: Mon, 12 Mar 2018 15:35:26 +0800 [thread overview]
Message-ID: <20180312073524.GM3217@dragon> (raw)
In-Reply-To: <20180311223203.3669-1-christophe.jaillet@wanadoo.fr>
+ Daniel
On Sun, Mar 11, 2018 at 11:32:03PM +0100, Christophe JAILLET wrote:
> 'ret' is known to be 0 at this point. It must be updated by the value
> returned by 'clk_prepare_enable()'.
>
> Fixes: 0a886f59528a ("drm: zte: add initial vou drm driver")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Acked-by: Shawn Guo <shawnguo@kernel.org>
next prev parent reply other threads:[~2018-03-12 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 22:32 [PATCH] drm: zte: Fix an error handling path in 'zx_crtc_bind()' Christophe JAILLET
2018-03-11 22:32 ` Christophe JAILLET
2018-03-12 7:35 ` Shawn Guo [this message]
2018-03-12 7:35 ` Shawn Guo
2018-03-12 7:35 ` Shawn Guo
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=20180312073524.GM3217@dragon \
--to=shawnguo@kernel.org \
--cc=airlied@linux.ie \
--cc=christophe.jaillet@wanadoo.fr \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.