From: "Farber, Eliav" <farbere@amazon.com>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: "Chocron, Jonathan" <jonnyc@amazon.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"mschmidt@redhat.com" <mschmidt@redhat.com>,
"calvin@wbinvd.org" <calvin@wbinvd.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] pps: clients: gpio: fix interrupt handling order in remove path
Date: Tue, 27 May 2025 09:11:48 +0000 [thread overview]
Message-ID: <d6358648c5b9420d8202bb9c23ac1824@amazon.com> (raw)
>> @@ -228,6 +228,7 @@ static void pps_gpio_remove(struct platform_device *pdev)
>> {
>> struct pps_gpio_device_data *data = platform_get_drvdata(pdev);
>>
>> + free_irq(data->irq, data);
>
> Why not just use devm_free_irq()?
As far as I understand, the main purpose of devm_*() is to provide
hands-off resource management. devm_request_irq() is intended to
eliminate the need for explicit cleanup in the remove() function by
automatically freeing the IRQ after remove() returns.
In my opinion, calling devm_free_irq() undermines the benefit of using
devm_request_irq() in the first place. If I need to explicitly free the
IRQ during remove(), then I’m no longer relying on devm’s automatic
cleanup - I’m effectively reverting to manual resource management while
still using devm-style registration, which I find unnecessary.
That said, if you still favor devm_free_irq(), I’ll revise the patch
accordingly.
Regards, Eliav
next reply other threads:[~2025-05-27 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 9:11 Farber, Eliav [this message]
2025-05-27 10:19 ` Rodolfo Giometti
2025-05-27 10:24 ` gregkh
-- strict thread matches above, loose matches on Subject: below --
2025-05-27 5:33 Eliav Farber
2025-05-27 8: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=d6358648c5b9420d8202bb9c23ac1824@amazon.com \
--to=farbere@amazon.com \
--cc=calvin@wbinvd.org \
--cc=giometti@enneenne.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonnyc@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=tglx@linutronix.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®