From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: fixes for DMA registration (3.3-rc)
Date: Thu, 01 Mar 2012 15:06:31 +0100 [thread overview]
Message-ID: <4F4F8267.5030408@atmel.com> (raw)
In-Reply-To: <201203011403.11369.arnd@arndb.de>
On 03/01/2012 03:03 PM, Arnd Bergmann :
> On Thursday 01 March 2012, Nicolas Ferre wrote:
>> As discussed on the mailing-list, we experience an out-of-sync situation
>> between the DMA controller driver and the related code in AT91 devices files.
>>
>> Those two patches already queued for 3.4 are correcting the problem that we found on
>> the current 3.3-rc kernels. I have tested that the DMA driver is registering well
>> with those fixes applied.
>>
>> Can you please pull them in a "fixes" branch and send them to Linus before 3.3-final?
>
> Hi Nicolas,
>
> I've just sent a pull request for bug fixes yesterday, so I'll wait
> until Linus has pulled that one and probably a few days before I
> send another one.
Sure.
> I have applied it to the fixes branch now but not updated the
> tag that I sent him.
Ok, thanks a lot for your quick help.
Best regards,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] at91: fixes for DMA registration (3.3-rc)
Date: Thu, 01 Mar 2012 15:06:31 +0100 [thread overview]
Message-ID: <4F4F8267.5030408@atmel.com> (raw)
In-Reply-To: <201203011403.11369.arnd@arndb.de>
On 03/01/2012 03:03 PM, Arnd Bergmann :
> On Thursday 01 March 2012, Nicolas Ferre wrote:
>> As discussed on the mailing-list, we experience an out-of-sync situation
>> between the DMA controller driver and the related code in AT91 devices files.
>>
>> Those two patches already queued for 3.4 are correcting the problem that we found on
>> the current 3.3-rc kernels. I have tested that the DMA driver is registering well
>> with those fixes applied.
>>
>> Can you please pull them in a "fixes" branch and send them to Linus before 3.3-final?
>
> Hi Nicolas,
>
> I've just sent a pull request for bug fixes yesterday, so I'll wait
> until Linus has pulled that one and probably a few days before I
> send another one.
Sure.
> I have applied it to the fixes branch now but not updated the
> tag that I sent him.
Ok, thanks a lot for your quick help.
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2012-03-01 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 10:05 at91: Error while registering DMA controller in 3.3-rc Nicolas Ferre
2012-03-01 10:05 ` Nicolas Ferre
2012-03-01 11:49 ` Arnd Bergmann
2012-03-01 11:49 ` Arnd Bergmann
2012-03-01 12:57 ` [GIT PULL] at91: fixes for DMA registration (3.3-rc) Nicolas Ferre
2012-03-01 14:03 ` Arnd Bergmann
2012-03-01 14:03 ` Arnd Bergmann
2012-03-01 14:06 ` Nicolas Ferre [this message]
2012-03-01 14:06 ` Nicolas Ferre
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=4F4F8267.5030408@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.