From: "Dan Williams" <dan.j.williams@intel.com>
To: "Guennadi Liakhovetski" <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com,
"Sascha Hauer" <s.hauer@pengutronix.de>,
linux-arm-kernel@lists.arm.linux.org.uk,
"Geert Uytterhoeven" <geert@linux-m68k.org>
Subject: Re: [PATCH 0/4 v6] i.MX31: dmaengine and framebuffer drivers
Date: Mon, 5 Jan 2009 12:43:13 -0700 [thread overview]
Message-ID: <e9c3a7c20901051143m37c0d7c0x5779475ddc7c5dc2@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812261714290.4895@axis700.grange>
On Fri, Dec 26, 2008 at 10:11 AM, Guennadi Liakhovetski
<g.liakhovetski@gmx.de> wrote:
> Hi,
>
> This is version 6 of dmaengine and framebuffer drivers for i.MX31.
>
Tha drivers/dma/ bits look ok to me minus the new warnings:
drivers/dma/ipu/ipu_irq.c: In function 'ipu_irq_fn':
drivers/dma/ipu/ipu_irq.c:328: warning: 'irq' may be used
uninitialized in this function
drivers/dma/ipu/ipu_irq.c: In function 'ipu_irq_err':
drivers/dma/ipu/ipu_irq.c:290: warning: 'irq' may be used
uninitialized in this function
I can take patches 1 and 2 through the async_tx tree, or if you would
rather, add my Acked-by to those and take 1-4 through the MXC tree.
I'll be sending the async_tx pull request for 2.6.29 in the next few
days.
Thanks,
Dan
next prev parent reply other threads:[~2009-01-05 19:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 17:11 Guennadi Liakhovetski
2008-12-26 17:11 ` [PATCH 1/4 v6] dmaengine: add async_tx_clear_ack() macro Guennadi Liakhovetski
2008-12-26 17:11 ` [PATCH 2/4 v6] i.MX31: Image Processing Unit DMA and IRQ drivers Guennadi Liakhovetski
2008-12-26 17:11 ` [PATCH 3/4 v6] i.MX31: framebuffer driver Guennadi Liakhovetski
2008-12-26 17:11 ` [PATCH 4/4 v6] i.MX31: platform bindings and initialisation for IPU and framebuffer drivers Guennadi Liakhovetski
2009-01-05 19:43 ` Dan Williams [this message]
2009-01-05 21:02 ` [PATCH 0/4 v6] i.MX31: dmaengine " Guennadi Liakhovetski
2009-01-05 21:35 ` Dan Williams
2009-01-16 10:09 ` Guennadi Liakhovetski
2009-01-16 17:39 ` Dan Williams
[not found] ` <Pine.LNX.4.64.0901162048400.9060@axis700.grange>
[not found] ` <4974F208.3020407@intel.com>
[not found] ` <Pine.LNX.4.64.0901201048090.5126@axis700.grange>
2009-02-19 14:41 ` [PATCH 3/4 v9] i.MX31: framebuffer driver Guennadi Liakhovetski
2009-02-19 18:36 ` Dan Williams
2009-02-25 21:54 ` Dan Williams
2009-02-26 7:37 ` Guennadi Liakhovetski
2009-02-26 18:41 ` Dan Williams
2009-02-26 20:34 ` Guennadi Liakhovetski
2009-02-27 0:36 ` Dan Williams
2009-01-06 9:04 ` [PATCH 0/4 v6] i.MX31: dmaengine and framebuffer drivers Sascha Hauer
2009-01-06 9:51 ` Guennadi Liakhovetski
2009-01-06 10:19 ` Sascha Hauer
2009-01-06 13:20 ` Hans J. Koch
2009-01-08 11:15 ` [PATCH 2/4 v7] i.MX31: Image Processing Unit DMA and IRQ drivers Guennadi Liakhovetski
2009-01-08 10:50 ` [PATCH 0/4 v6] i.MX31: dmaengine and framebuffer drivers Sascha Hauer
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=e9c3a7c20901051143m37c0d7c0x5779475ddc7c5dc2@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=adaplas@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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®