From: Chris Ball <cjb@laptop.org>
To: Ludovic Desroches <ludovic.desroches@atmel.com>
Cc: linux-mmc@vger.kernel.org, "Ferre,
Nicolas" <nicolas.ferre@atmel.com>,
plagnioj@jcrosoft.com, me@danielpalmer.co.uk,
linux-arm-kernel@lists.infradead.org
Subject: Re: atmel-mci causing oops?
Date: Wed, 29 Feb 2012 12:35:52 -0500 [thread overview]
Message-ID: <m2linlo83r.fsf@bob.laptop.org> (raw)
In-Reply-To: <20120229173115.GA23529@ldesroches-Latitude-E6320> (Ludovic Desroches's message of "Wed, 29 Feb 2012 18:31:15 +0100")
Hi Ludovic,
On Wed, Feb 29 2012, Ludovic Desroches wrote:
> You can find the two patches into the mmc-next tree of Chris:
> http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commit;h=43df92914ea0623893bcb801791d5d2be2f5e015
> http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commit;h=9cfa4030ea90f2fc204532975a824b987433f6dd
>
> By the way, Chris, is it possible to put these patches as a fix for 3.3
> kernel? Without them we will have this oops each time someone would use
> mmc without a DMA Controller or if it is impossible to get a dma channel.
Will do, thanks. Should they go to 3.2-stable, too?
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-02-29 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 17:31 atmel-mci causing oops? Ludovic Desroches
2012-02-29 17:35 ` Chris Ball [this message]
2012-02-29 21:44 ` Ludovic Desroches
-- strict thread matches above, loose matches on Subject: below --
2012-02-27 0:49 Daniel Palmer
2012-02-27 1:30 ` Seungwon Jeon
2012-02-27 1:57 ` Daniel Palmer
2012-02-27 3:28 ` Seungwon Jeon
2012-02-27 11:58 ` Daniel Palmer
2012-02-27 1:48 ` Jaehoon Chung
2012-02-27 2:20 ` Daniel Palmer
2012-02-27 2:47 ` Jaehoon Chung
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=m2linlo83r.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=me@danielpalmer.co.uk \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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;
as well as URLs for NNTP newsgroup(s).