From: Andi Shyti <andi.shyti@linux.intel.com>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: intel-gfx@lists.freedesktop.org,
Abaci Robot <abaci@linux.alibaba.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
rodrigo.vivi@intel.com
Subject: Re: [Intel-gfx] [PATCH -next] drm/i915: remove unreachable code
Date: Wed, 31 May 2023 11:22:16 +0200 [thread overview]
Message-ID: <ZHcRyNg1aGHJOBSB@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230531021714.125078-1-yang.lee@linux.alibaba.com>
Hi Yang,
On Wed, May 31, 2023 at 10:17:14AM +0800, Yang Li wrote:
> The code after the return will not be executed, so remove them.
>
> Eliminate the following warning:
> drivers/gpu/drm/i915/display/intel_color.c:1808 intel_color_prepare_commit() warn: ignoring unreachable code.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=5342
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---
> drivers/gpu/drm/i915/display/intel_color.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_color.c b/drivers/gpu/drm/i915/display/intel_color.c
> index 8966e6560516..0bfebac1e3e2 100644
> --- a/drivers/gpu/drm/i915/display/intel_color.c
> +++ b/drivers/gpu/drm/i915/display/intel_color.c
> @@ -1804,11 +1804,6 @@ void intel_color_prepare_commit(struct intel_crtc_state *crtc_state)
>
> /* FIXME DSB has issues loading LUTs, disable it for now */
> return;
> -
> - if (!crtc_state->pre_csc_lut && !crtc_state->post_csc_lut)
> - return;
> -
> - crtc_state->dsb = intel_dsb_prepare(crtc, 1024);
yeah... it's an ugly bit, from my side:
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
but would be nice to hear from Ville who has added the return in
a first place.
Andi
> }
>
> void intel_color_cleanup_commit(struct intel_crtc_state *crtc_state)
> --
> 2.20.1.7.g153144c
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: airlied@gmail.com, intel-gfx@lists.freedesktop.org,
Abaci Robot <abaci@linux.alibaba.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
daniel@ffwll.ch, rodrigo.vivi@intel.com,
Ville Syrjala <ville.syrjala@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH -next] drm/i915: remove unreachable code
Date: Wed, 31 May 2023 11:22:16 +0200 [thread overview]
Message-ID: <ZHcRyNg1aGHJOBSB@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230531021714.125078-1-yang.lee@linux.alibaba.com>
Hi Yang,
On Wed, May 31, 2023 at 10:17:14AM +0800, Yang Li wrote:
> The code after the return will not be executed, so remove them.
>
> Eliminate the following warning:
> drivers/gpu/drm/i915/display/intel_color.c:1808 intel_color_prepare_commit() warn: ignoring unreachable code.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=5342
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---
> drivers/gpu/drm/i915/display/intel_color.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_color.c b/drivers/gpu/drm/i915/display/intel_color.c
> index 8966e6560516..0bfebac1e3e2 100644
> --- a/drivers/gpu/drm/i915/display/intel_color.c
> +++ b/drivers/gpu/drm/i915/display/intel_color.c
> @@ -1804,11 +1804,6 @@ void intel_color_prepare_commit(struct intel_crtc_state *crtc_state)
>
> /* FIXME DSB has issues loading LUTs, disable it for now */
> return;
> -
> - if (!crtc_state->pre_csc_lut && !crtc_state->post_csc_lut)
> - return;
> -
> - crtc_state->dsb = intel_dsb_prepare(crtc, 1024);
yeah... it's an ugly bit, from my side:
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
but would be nice to hear from Ville who has added the return in
a first place.
Andi
> }
>
> void intel_color_cleanup_commit(struct intel_crtc_state *crtc_state)
> --
> 2.20.1.7.g153144c
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: intel-gfx@lists.freedesktop.org,
Abaci Robot <abaci@linux.alibaba.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
daniel@ffwll.ch, rodrigo.vivi@intel.com, airlied@gmail.com
Subject: Re: [Intel-gfx] [PATCH -next] drm/i915: remove unreachable code
Date: Wed, 31 May 2023 11:22:16 +0200 [thread overview]
Message-ID: <ZHcRyNg1aGHJOBSB@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230531021714.125078-1-yang.lee@linux.alibaba.com>
Hi Yang,
On Wed, May 31, 2023 at 10:17:14AM +0800, Yang Li wrote:
> The code after the return will not be executed, so remove them.
>
> Eliminate the following warning:
> drivers/gpu/drm/i915/display/intel_color.c:1808 intel_color_prepare_commit() warn: ignoring unreachable code.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=5342
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---
> drivers/gpu/drm/i915/display/intel_color.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_color.c b/drivers/gpu/drm/i915/display/intel_color.c
> index 8966e6560516..0bfebac1e3e2 100644
> --- a/drivers/gpu/drm/i915/display/intel_color.c
> +++ b/drivers/gpu/drm/i915/display/intel_color.c
> @@ -1804,11 +1804,6 @@ void intel_color_prepare_commit(struct intel_crtc_state *crtc_state)
>
> /* FIXME DSB has issues loading LUTs, disable it for now */
> return;
> -
> - if (!crtc_state->pre_csc_lut && !crtc_state->post_csc_lut)
> - return;
> -
> - crtc_state->dsb = intel_dsb_prepare(crtc, 1024);
yeah... it's an ugly bit, from my side:
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
but would be nice to hear from Ville who has added the return in
a first place.
Andi
> }
>
> void intel_color_cleanup_commit(struct intel_crtc_state *crtc_state)
> --
> 2.20.1.7.g153144c
next prev parent reply other threads:[~2023-05-31 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 2:17 [PATCH -next] drm/i915: remove unreachable code Yang Li
2023-05-31 2:17 ` [Intel-gfx] " Yang Li
2023-05-31 2:17 ` Yang Li
2023-05-31 9:22 ` Andi Shyti [this message]
2023-05-31 9:22 ` [Intel-gfx] " Andi Shyti
2023-05-31 9:22 ` Andi Shyti
2023-05-31 15:32 ` kernel test robot
2023-05-31 15:32 ` [Intel-gfx] " kernel test robot
2023-05-31 15:32 ` kernel test robot
2023-05-31 16:13 ` kernel test robot
2023-05-31 16:13 ` [Intel-gfx] " kernel test robot
2023-05-31 16:13 ` kernel test robot
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=ZHcRyNg1aGHJOBSB@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=abaci@linux.alibaba.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=yang.lee@linux.alibaba.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 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.