From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 0/2] parport: Convert to platform remove callback returning void
Date: Sat, 17 Feb 2024 09:00:00 +0100 [thread overview]
Message-ID: <2024021747-maggot-onto-30a8@gregkh> (raw)
In-Reply-To: <cf6vlgvbbtsofdladgeqenrf5bqpn2p3vhzu2llwuu4ee5tk6i@w4h6jjexeulj>
On Thu, Feb 15, 2024 at 10:22:09PM +0100, Uwe Kleine-König wrote:
> Hello,
>
> [Cc += gregkh]
>
> On Mon, Dec 18, 2023 at 10:05:17PM +0100, Uwe Kleine-König wrote:
> > this series converts all drivers below drivers/parport to use
> > .remove_new(). See commit 5c5a7680e67b ("platform: Provide a remove
> > callback that returns no value") for an extended explanation and the
> > eventual goal. The TL;DR; is to make it harder for driver authors to
> > leak resources without noticing.
> >
> > This is merge window material. The two patches are independent of each
> > other, so they could be applied individually.
> >
> > Best regards
> > Uwe
> >
> > Uwe Kleine-König (2):
> > parport: amiga: Convert to platform remove callback returning void
> > parport: sunbpp: Convert to platform remove callback returning void
>
> I got no feedback for these patches since they were sent two months ago
> :-\
>
> Looking at the last patches to drivers/parport, they were merged by
> Greg. Given the patches weren't sent to him, should I resend?
I can just take them directly from here, thanks!
greg k-h
prev parent reply other threads:[~2024-02-17 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 21:05 [PATCH 0/2] parport: Convert to platform remove callback returning void Uwe Kleine-König
2023-12-18 21:05 ` [PATCH 1/2] parport: amiga: " Uwe Kleine-König
2023-12-18 21:05 ` [PATCH 2/2] parport: sunbpp: " Uwe Kleine-König
2024-02-15 21:22 ` [PATCH 0/2] parport: " Uwe Kleine-König
2024-02-17 8:00 ` Greg Kroah-Hartman [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=2024021747-maggot-onto-30a8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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