Linux-Aspeed Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 00/53] drm: Convert to platform remove callback returning void
Date: Thu, 1 Jun 2023 17:40:02 +0200	[thread overview]
Message-ID: <20230601154002.uv2wfatpb7b45duz@pengutronix.de> (raw)
In-Reply-To: <20230507162616.1368908-1-u.kleine-koenig@pengutronix.de>

Hello,

On Sun, May 07, 2023 at 06:25:23PM +0200, Uwe Kleine-K?nig wrote:
> this patch series adapts the platform drivers below drivers/gpu/drm
> to use the .remove_new() callback. Compared to the traditional .remove()
> callback .remove_new() returns no value. This is a good thing because
> the driver core doesn't (and cannot) cope for errors during remove. The
> only effect of a non-zero return value in .remove() is that the driver
> core emits a warning. The device is removed anyhow and an early return
> from .remove() usually yields a resource leak.
> 
> By changing the remove callback to return void driver authors cannot
> reasonably (but wrongly) assume any more that there happens some kind of
> cleanup later.

I wonder if someone would volunteer to add the whole series to
drm-misc-next?!

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/linux-aspeed/attachments/20230601/da6cc783/attachment-0001.sig>

  parent reply	other threads:[~2023-06-01 15:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-07 16:25 [PATCH 00/53] drm: Convert to platform remove callback returning void Uwe Kleine-König
2023-05-07 16:25 ` [PATCH 05/53] drm/aspeed: " Uwe Kleine-König
2023-05-08  7:06 ` [PATCH 00/53] drm: " Thomas Zimmermann
2023-05-08  7:50   ` Uwe Kleine-König
2023-05-15  7:50 ` Inki Dae
2023-05-15  9:20   ` Uwe Kleine-König
2023-06-01 15:40 ` Uwe Kleine-König [this message]
2023-06-08 16:08   ` Doug Anderson
2023-06-08 16:26     ` Laurent Pinchart
2023-06-08 16:47       ` Doug Anderson
2023-06-08 17:19       ` Tomi Valkeinen
2023-06-08 17:38         ` Doug Anderson
2023-06-17 16:12     ` patches dropped from drm-misc-next [Was: Re: [PATCH 00/53] drm: Convert to platform remove callback returning] void Uwe Kleine-König
2023-06-17 16:51       ` Chen-Yu Tsai
2023-06-17 17:57       ` Doug Anderson
2023-06-18 12:39         ` Uwe Kleine-König
2023-06-18 14:02           ` Uwe Kleine-König
2023-06-18 14:32           ` Maxime Ripard
2023-06-18 16:29             ` Uwe Kleine-König
2023-06-19  9:45               ` Maxime Ripard
2023-06-19 10:53                 ` Uwe Kleine-König
2023-06-19 12:47                   ` Maxime Ripard
2023-06-19 13:25                     ` Geert Uytterhoeven
2023-06-19 14:02                       ` Maxime Ripard
2023-06-19 14:20                         ` Geert Uytterhoeven
2023-06-19 13:58                     ` Uwe Kleine-König
2023-09-09 14:37 ` [PATCH 00/53] drm: Convert to platform remove callback returning void Javier Martinez Canillas

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=20230601154002.uv2wfatpb7b45duz@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-aspeed@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox