From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: David Brownell <david-b@pacbell.net>,
linux-arm-kernel@lists.arm.linux.org.uk,
Andrew Victor <linux@maxim.org.za>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] at91_mci: use generic GPIO calls
Date: Thu, 7 Feb 2008 18:10:22 +0100 [thread overview]
Message-ID: <20080207181022.5ba37443@poseidon.drzeus.cx> (raw)
In-Reply-To: <47A74790.50207@atmel.com>
On Mon, 04 Feb 2008 18:12:48 +0100
Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> From: David Brownell <dbrownell@users.sourceforge.net>
>
> Update the AT91 MMC driver to use the generic GPIO calls instead of the
> AT91-specific calls; and to request (and release) those GPIO signals.
>
> That required updating the probe() fault cleanup codepaths. Now there
> is a single sequence for freeing resources, in reverse order of their
> allocation. Also that code uses use dev_*() for messaging, and has less
> abuse of KERN_ERR.
>
> Likewise with updating remove() cleanup. This had to free the GPIOs,
> and while adding that code I noticed and fixed two other problems: it
> was poking at a workqueue owned by the mmc core; and in one (rare)
> case would try freeing an IRQ that it didn't allocate.
>
> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
Applied thanks.
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
prev parent reply other threads:[~2008-02-07 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200802011901.27532.david-b@pacbell.net>
2008-02-04 17:12 ` Nicolas Ferre
2008-02-05 9:53 ` Marc Pignat
2008-02-05 10:07 ` David Brownell
2008-02-07 17:10 ` Pierre Ossman [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=20080207181022.5ba37443@poseidon.drzeus.cx \
--to=drzeus-mmc@drzeus.cx \
--cc=david-b@pacbell.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
/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®