From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: Nicolas Ferre <nicolas.ferre@atmel.com>,
David Brownell <david-b@pacbell.net>
Cc: lkml <linux-kernel@vger.kernel.org>,
peterz@infradead.org, Ingo Molnar <mingo@elte.hu>,
Russell King <rmk@arm.linux.org.uk>,
Nicolas Ferre <nicolas.ferre@rfo.atmel.com>,
Andrew Victor <linux@maxim.org.za>
Subject: Re: [patch 2.6.28-rc2] at91_mci: workaround lockdep
Date: Wed, 19 Nov 2008 19:45:17 +0100 [thread overview]
Message-ID: <20081119194517.2b73d74f@mjolnir.drzeus.cx> (raw)
In-Reply-To: <4921394E.2000901@atmel.com>
On Mon, 17 Nov 2008 10:28:46 +0100
Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
>
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>
Any side-effects besides from dmesg noise? IOW should I push for .28?
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
next prev parent reply other threads:[~2008-11-19 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 21:26 [patch 2.6.28-rc2] at91_mci: workaround lockdep David Brownell
2008-10-28 17:04 ` Peter Zijlstra
2008-10-28 17:22 ` David Brownell
2008-10-28 17:36 ` Peter Zijlstra
2008-10-28 19:41 ` David Brownell
2008-10-29 7:20 ` David Brownell
2008-11-03 13:47 ` Nicolas Ferre
2008-11-17 9:28 ` Nicolas Ferre
2008-11-19 18:45 ` Pierre Ossman [this message]
2008-11-20 15:02 ` Nicolas Ferre
2008-11-20 15:42 ` Pierre Ossman
2008-11-23 14:26 ` Peter Zijlstra
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=20081119194517.2b73d74f@mjolnir.drzeus.cx \
--to=drzeus-mmc@drzeus.cx \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=mingo@elte.hu \
--cc=nicolas.ferre@atmel.com \
--cc=nicolas.ferre@rfo.atmel.com \
--cc=peterz@infradead.org \
--cc=rmk@arm.linux.org.uk \
/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