From: Andrew Morton <akpm@linux-foundation.org>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: Ladislav.Michl@seznam.cz,
Jarkko Lavinen <jarkko.lavinen@nokia.com>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmci-omap: free irq resource
Date: Mon, 9 Nov 2009 14:27:49 -0800 [thread overview]
Message-ID: <20091109142749.0d8f6967.akpm@linux-foundation.org> (raw)
In-Reply-To: <20091101115905.GB15144@localhost.localdomain>
On Sun, 1 Nov 2009 12:59:05 +0100
Ladislav.Michl@seznam.cz wrote:
> Free IRQ on remove.
>
> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> Acked-by: Tony Lindgren <tony@atomide.com>
>
> diff --git a/drivers/mmc/host/omap.c b/drivers/mmc/host/omap.c
> index 5d773b8..5f970e2 100644
> --- a/drivers/mmc/host/omap.c
> +++ b/drivers/mmc/host/omap.c
> @@ -1529,6 +1529,7 @@ static int mmc_omap_remove(struct platform_device *pdev)
> host->pdata->cleanup(&pdev->dev);
>
> mmc_omap_fclk_enable(host, 0);
> + free_irq(host->irq, host);
> clk_put(host->fclk);
> clk_disable(host->iclk);
> clk_put(host->iclk);
This is a poor changelog.
The reader doesn't know what the implication of the bug is. I _assume_
that it means that the driver can only be loaded a single time. That
on a second modprobe, it fails to allocate the interrupt and fails.
In which case this is a fairly serious bug and perhaps the patch should
be backported into the -stable tree.
Or I could be all wrong about all of that. This is why it's better if
the patch submitter *explains* these things, rather than leaving others
to guess.
next prev parent reply other threads:[~2009-11-09 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 11:59 [PATCH] mmci-omap: free irq resource Ladislav.Michl
2009-11-09 22:27 ` Andrew Morton [this message]
2009-11-18 19:05 ` Ladislav Michl
-- strict thread matches above, loose matches on Subject: below --
2009-11-01 11:56 Ladislav.Michl
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=20091109142749.0d8f6967.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Ladislav.Michl@seznam.cz \
--cc=jarkko.lavinen@nokia.com \
--cc=ladis@linux-mips.org \
--cc=linux-mmc@vger.kernel.org \
/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