The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: neil.armstrong@linaro.org
To: Michail Tatas <michail.tatas@gmail.com>,
	michael@amarulasolutions.com, jesszhan0024@gmail.com,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
	dianders@chromium.org
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] drm/panel: ilitek-ili9805: make cleanup funcs void
Date: Mon, 20 Jul 2026 14:40:11 +0200	[thread overview]
Message-ID: <f8ba765c-bd64-4a2a-808f-ce7b2721ed89@linaro.org> (raw)
In-Reply-To: <20260719190358.438699-4-michail.tatas@gmail.com>

On 7/19/26 21:03, Michail Tatas wrote:
> Make cleanup functions return void since no one is checking
> their return values
> 
> Signed-off-by: Michail Tatas <michail.tatas@gmail.com>
> ---
>   drivers/gpu/drm/panel/panel-ilitek-ili9805.c | 8 ++------
>   1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/panel/panel-ilitek-ili9805.c b/drivers/gpu/drm/panel/panel-ilitek-ili9805.c
> index a70b9512746a..64cfaf981e9f 100644
> --- a/drivers/gpu/drm/panel/panel-ilitek-ili9805.c
> +++ b/drivers/gpu/drm/panel/panel-ilitek-ili9805.c
> @@ -148,13 +148,11 @@ static int ili9805_power_on(struct ili9805 *ctx)
>   	return 0;
>   }
>   
> -static int ili9805_power_off(struct ili9805 *ctx)
> +static void ili9805_power_off(struct ili9805 *ctx)
>   {
>   	gpiod_set_value(ctx->reset_gpio, 0);
>   	regulator_disable(ctx->dvdd);
>   	regulator_disable(ctx->avdd);
> -
> -	return 0;
>   }
>   
>   static int ili9805_activate(struct ili9805 *ctx)
> @@ -188,15 +186,13 @@ static int ili9805_prepare(struct drm_panel *panel)
>   	return 0;
>   }
>   
> -static int ili9805_deactivate(struct ili9805 *ctx)
> +static void ili9805_deactivate(struct ili9805 *ctx)
>   {
>   	struct mipi_dsi_multi_context dsi_ctx = { .dsi = ctx->dsi };
>   
>   	mipi_dsi_dcs_set_display_off_multi(&dsi_ctx);
>   	mipi_dsi_usleep_range(&dsi_ctx, 5000, 10000);
>   	mipi_dsi_dcs_enter_sleep_mode_multi(&dsi_ctx);
> -
> -	return dsi_ctx.accum_err;
>   }
>   
>   static int ili9805_unprepare(struct drm_panel *panel)

Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>

Thanks,
Neil

  reply	other threads:[~2026-07-20 12:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-19 19:03 [PATCH v2 0/3] drm/panel: ilitek-ili9805: convert to *_multi API Michail Tatas
2026-07-19 19:03 ` [PATCH v2 1/3] drm/panel: ilitek-ili9805: Use _multi variants Michail Tatas
2026-07-20 12:38   ` neil.armstrong
2026-07-20 20:07   ` Doug Anderson
2026-07-19 19:03 ` [PATCH v2 2/3] drm/panel: ilitek-ili9805: Use dsi_multi in init Michail Tatas
2026-07-20 12:39   ` neil.armstrong
2026-07-20 20:08   ` Doug Anderson
2026-07-21 17:32     ` Michail Tatas
2026-07-19 19:03 ` [PATCH v2 3/3] drm/panel: ilitek-ili9805: make cleanup funcs void Michail Tatas
2026-07-20 12:40   ` neil.armstrong [this message]
2026-07-20 20:08   ` Doug Anderson

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=f8ba765c-bd64-4a2a-808f-ce7b2721ed89@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=airlied@gmail.com \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jesszhan0024@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=michael@amarulasolutions.com \
    --cc=michail.tatas@gmail.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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