From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-mips@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] MIPS: PCI: Convert to platform remove callback returning void
Date: Tue, 20 Jun 2023 14:51:02 +0200 [thread overview]
Message-ID: <20230620125102.GD10520@alpha.franken.de> (raw)
In-Reply-To: <20230616165127.1055386-1-u.kleine-koenig@pengutronix.de>
On Fri, Jun 16, 2023 at 06:51:27PM +0200, 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() is renamed to .remove().
>
> Trivially convert this driver from always returning zero in the remove
> callback to the void returning variant.
>
> While destroying alignment of the assignments in bridge_driver, do it
> consistently and use a single space before =.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> arch/mips/pci/pci-xtalk-bridge.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2023-06-20 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 16:51 [PATCH] MIPS: PCI: Convert to platform remove callback returning void Uwe Kleine-König
2023-06-20 12:51 ` Thomas Bogendoerfer [this message]
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=20230620125102.GD10520@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=kernel@pengutronix.de \
--cc=linux-mips@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;
as well as URLs for NNTP newsgroup(s).