All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ludovic Desroches <ludovic.desroches@atmel.com>
To: Chris Ball <cjb@laptop.org>
Cc: Ludovic Desroches <ludovic.desroches@atmel.com>,
	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 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


WARNING: multiple messages have this Message-ID (diff)
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

  reply	other threads:[~2012-02-29 21:45 UTC|newest]

Thread overview: 13+ 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
2012-02-29 17:35   ` Chris Ball
2012-02-29 21:44   ` Ludovic Desroches [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=4F4E9C57.9020502@atmel.com \
    --to=ludovic.desroches@atmel.com \
    --cc=cjb@laptop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.