mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rodolfo Giometti <giometti@enneenne.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] pps: clients: gpio: Convert to platform remove callback returning void
Date: Thu, 9 May 2024 09:41:45 +0200	[thread overview]
Message-ID: <bd4799ab-9456-421a-8294-de6481543ad1@enneenne.com> (raw)
In-Reply-To: <v7sefhmq42ro2dfpxgipxxajxpuh3xy46c77uibmypyp34duqs@5vw5ava4ns7d>

On 08/05/24 15:57, Uwe Kleine-König wrote:
> On Fri, Apr 12, 2024 at 02:26:48PM +0200, Uwe Kleine-König wrote:
>> [Cc: += linuxpps@ml.enneenne.com]
>>
>> On Fri, Mar 08, 2024 at 09:57:29AM +0100, Rodolfo Giometti wrote:
>>> On 08/03/24 09:51, 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>
>>>
>>> Acked-by: Rodolfo Giometti <giometti@enneenne.com>
>>
>> The MAINTAINERS entry for drivers/pps lists you as single maintainer.
>> Who is expected to pick up this patch given that you "only" send an ack
>> but didn't pick up the patch? (Or only picked it up in a tree not
>> included in next.)
> 
> In the meantime you sent an Ack to my patch. Does that mean I can/should
> include this patch in the series changing struct platform_driver that I
> intend to send to Greg after the upcoming merge window closes?

Yes.

Rodolfo

-- 
GNU/Linux Solutions                  e-mail: giometti@enneenne.com
Linux Device Driver                          giometti@linux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming


  reply	other threads:[~2024-05-09  7:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  8:51 Uwe Kleine-König
2024-03-08  8:57 ` Rodolfo Giometti
2024-04-12 12:26   ` Uwe Kleine-König
2024-04-12 13:03     ` Rodolfo Giometti
2024-05-08 13:57     ` Uwe Kleine-König
2024-05-09  7:41       ` Rodolfo Giometti [this message]
2024-04-12 13:00 ` Rodolfo Giometti

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=bd4799ab-9456-421a-8294-de6481543ad1@enneenne.com \
    --to=giometti@enneenne.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®