From: ludovic.desroches@atmel•com (Ludovic Desroches)
To: linux-arm-kernel@lists•infradead.org
Subject: atmel-mci causing oops?
Date: Wed, 29 Feb 2012 22:44:55 +0100 [thread overview]
Message-ID: <4F4E9C57.9020502@atmel.com> (raw)
In-Reply-To: <m2linlo83r.fsf@bob.laptop.org>
Hi Chris,
On 02/29/2012 06:35 PM, Chris Ball wrote:
> 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.
You're right 3.2 kernel is also concerned so they can go to 3.2-stable.
Thanks.
Ludovic
prev parent reply other threads:[~2012-02-29 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120229173115.GA23529@ldesroches-Latitude-E6320>
2012-02-29 17:35 ` atmel-mci causing oops? Chris Ball
2012-02-29 21:44 ` Ludovic Desroches [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=4F4E9C57.9020502@atmel.com \
--to=ludovic.desroches@atmel$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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