From: Dan Williams <dan.j.williams@intel.com>
To: Li Yang <leoli@freescale.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
linuxppc-dev Development <linuxppc-dev@ozlabs.org>,
Kumar Gala <galak@kernel.crashing.org>,
Ira Snyder <iws@ovro.caltech.edu>
Subject: Re: [GIT PULL] fsldma driver fixes
Date: Tue, 26 May 2009 16:59:23 -0700 [thread overview]
Message-ID: <e9c3a7c20905261659v5d785df3w646efd4cbba2e6dd@mail.gmail.com> (raw)
In-Reply-To: <2a27d3730905220347s59dbd152kc69c8399693ae307@mail.gmail.com>
On Fri, May 22, 2009 at 3:47 AM, Li Yang <leoli@freescale.com> wrote:
> Hi Dan,
>
> Here are fixes for Freescale DMA engine driver.
>
> Thanks,
> - Leo
>
>
> The following changes since commit 5805977e63a36ad56594a623f3bd2bebcb7db233:
> Linus Torvalds (1):
> Merge branch 'for-linus' of git://git.kernel.org/.../jbarnes/drm-2.6
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/leo/fsl-soc.git fsldma
>
> Ira Snyder (4):
> fsldma: fix "DMA halt timeout!" errors
> fsldma: fix infinite loop on multi-descriptor DMA chain completion
> fsldma: snooping is not enabled for last entry in descriptor chain
> fsldma: fix memory leak on error path in fsl_dma_prep_memcpy()
>
> Li Yang (1):
> fsldma: update mailling list address in MAINTAINERS
>
> Roel Kluin (1):
> fsldma: fix check on potential fdev->chan[] overflow
>
Pulled, thanks. These all look like 2.6.30 candidates, right? I'll
send these upstream in the next few days as I have not heard back from
Kumar on taking fsldma patches through his tree [1].
Thanks,
Dan
[1]: http://marc.info/?l=linux-kernel&m=124225089507475&w=2
next prev parent reply other threads:[~2009-05-27 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 10:47 Li Yang
2009-05-26 23:59 ` Dan Williams [this message]
2009-05-27 8:24 ` Li Yang
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=e9c3a7c20905261659v5d785df3w646efd4cbba2e6dd@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=galak@kernel.crashing.org \
--cc=iws@ovro.caltech.edu \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®