From: Chris Ball <cjb@laptop.org>
To: Ludovic Desroches <ludovic.desroches@atmel.com>
Cc: Johan Hovold <jhovold@gmail.com>,
linux-mmc@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-kernel@vger.kernel.org, stable <stable@vger.kernel.org>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Hans-Christian Egtvedt <egtvedt@samfundet.no>
Subject: Re: [PATCH] ARM: at91/avr32/atmel-mci: fix DMA-channel leak on module unload
Date: Fri, 22 Mar 2013 12:58:35 -0400 [thread overview]
Message-ID: <87ehf7mkw4.fsf@octavius.laptop.org> (raw)
In-Reply-To: <46568.1708221838$1363345027@news.gmane.org> (Ludovic Desroches's message of "Fri, 15 Mar 2013 11:56:06 +0100")
Hi,
On Fri, Mar 15 2013, Ludovic Desroches wrote:
> On Wed, Mar 13, 2013 at 05:11:59PM +0100, Johan Hovold wrote:
>> Fix regression introduced by commit 796211b7953 ("mmc: atmel-mci: add
>> pdc support and runtime capabilities detection") which removed the need
>> for CONFIG_MMC_ATMELMCI_DMA but kept the Kconfig-entry as well as the
>> compile guards around dma_release_channel() in remove(). Consequently,
>> DMA is always enabled (if supported), but the DMA-channel is not
>> released on module unload unless the DMA-config option is selected.
>>
>> Remove the no longer used CONFIG_MMC_ATMELMCI_DMA option completely.
>>
>> Cc: stable <stable@vger.kernel.org>
>> Signed-off-by: Johan Hovold <jhovold@gmail.com>
>
> Hi Johan,
>
> Good point so
>
> Acked-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Thanks, I'll merge this via the MMC tree if no-one objects.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2013-03-22 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 16:11 [PATCH] ARM: at91/avr32/atmel-mci: fix DMA-channel leak on module unload Johan Hovold
2013-03-15 10:56 ` Ludovic Desroches
2013-03-22 16:58 ` Chris Ball [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=87ehf7mkw4.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=egtvedt@samfundet.no \
--cc=hskinnemoen@gmail.com \
--cc=jhovold@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=stable@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