All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	alexander.shishkin@linux.intel.com
Subject: Re: [PATCH 7/8] intel_th: Convert to platform remove callback returning void
Date: Wed, 21 Feb 2024 20:50:32 +0200	[thread overview]
Message-ID: <87edd5y7lz.fsf@ubik.fi.intel.com> (raw)
In-Reply-To: <qiiln66o6uy2nsqdjcykygp3yumonn7jqp7q4wxf56i6pazics@iqfaiglmsgwt>

Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:

> Hello Greg,
>
> On Thu, Feb 15, 2024 at 10:16:41PM +0100, Uwe Kleine-König wrote:
>> On Wed, Jan 10, 2024 at 09:41:54AM +0100, Uwe Kleine-König wrote:
>> > On Tue, Nov 07, 2023 at 09:28:26PM +0100, Uwe Kleine-König wrote:
>> > > The .remove() callback for a platform driver returns an int which makes
>> > > many driver authors wrongly assume it's possible to do error handling by
>> > > returning an error code. However the value returned is ignored (apart
>> > > from emitting a warning) and this typically results in resource leaks.
>> > > 
>> > > To improve here there is a quest to make the remove callback return
>> > > void. In the first step of this quest all drivers are converted to
>> > > .remove_new(), which already returns void. Eventually after all drivers
>> > > are converted, .remove_new() will be renamed to .remove().
>> > > 
>> > > Trivially convert this driver from always returning zero in the remove
>> > > callback to the void returning variant.
>> > > 
>> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>> > 
>> > I didn't get any feedback to this patch and it didn't make it into next
>> > up to now.
>> > 
>> > Is this still on someone's radar?
>> 
>> Is there a chance to get this patch into v6.9-rc1? Are you the right one
>> to talk to about this patch? (According to MAINTAINERS you are.)
>> 
>> The patch was sent during the 6.7 merge window and now already missed
>> the 6.8 one :-\
>
> I failed in several attempts to get feedback on this patch. You applied
> the last two patches for this driver (that is all patches since the
> driver was born). Would you care for that one, too? Tell me if you want
> a resend. Note that the other 7 patches from this series are already
> cared for, so if you're using b4 am or shazam, make use of -P7.

Apologies. This looks good to me, I will pick it up for my next
submission to Greg unless somebody objects.

Regards,
--
Alex

  reply	other threads:[~2024-02-21 18:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 20:28 [PATCH 0/8] hwtracing: Convert to platform remove callback returning void Uwe Kleine-König
2023-11-07 20:28 ` [PATCH 1/8] coresight: ultrasoc-smb: Fix resource leak in .remove() Uwe Kleine-König
2023-11-09  9:41   ` hejunhao
2023-11-09  9:53     ` Uwe Kleine-König
2023-11-09 12:14       ` hejunhao
2023-11-09 13:11         ` Uwe Kleine-König
2023-11-16 12:35           ` hejunhao
2023-11-16 13:52             ` Suzuki K Poulose
2023-11-07 20:28 ` [PATCH 2/8] coresight: dummy: Convert to platform remove callback returning void Uwe Kleine-König
2023-11-07 20:28 ` [PATCH 3/8] coresight: etm4x: " Uwe Kleine-König
2023-11-07 20:28 ` [PATCH 4/8] coresight: funnel: " Uwe Kleine-König
2023-11-07 20:28 ` [PATCH 5/8] coresight: replicator: " Uwe Kleine-König
2023-11-07 20:28 ` [PATCH 6/8] coresight: trbe: " Uwe Kleine-König
2023-11-07 20:28 ` [PATCH 7/8] intel_th: " Uwe Kleine-König
2024-01-10  8:41   ` Uwe Kleine-König
2024-02-15 21:16     ` Uwe Kleine-König
2024-02-21  7:19       ` Uwe Kleine-König
2024-02-21 18:50         ` Alexander Shishkin [this message]
2024-04-11  7:07           ` Uwe Kleine-König
2024-04-15  6:48             ` Alexander Shishkin
2024-04-29  7:13               ` Uwe Kleine-König
2024-04-29 12:22                 ` Alexander Shishkin
2024-04-29 12:30                   ` Alexander Shishkin
2024-04-29 13:07                     ` Alexander Shishkin
2023-11-07 20:28 ` [PATCH 8/8] coresight: ultrasoc-smb: " Uwe Kleine-König
2023-11-09 11:13 ` [PATCH 0/8] hwtracing: " James Clark

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=87edd5y7lz.fsf@ubik.fi.intel.com \
    --to=alexander.shishkin@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.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 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.