From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] OMAP2/3: DMA: FIFO drain errata fixes
Date: Mon, 4 Oct 2010 09:57:42 -0700 [thread overview]
Message-ID: <20101004165742.GT3117@atomide.com> (raw)
In-Reply-To: <201010041133.37450.peter.ujfalusi@nokia.com>
* Peter Ujfalusi <peter.ujfalusi@nokia.com> [101004 01:26]:
> On Monday 04 October 2010 11:29:16 ext Peter Ujfalusi wrote:
> > Hello,
> >
> > Will resend, since
>
> I'll wait for comments on v4 series, and I'll send the v5 later today after the
> comments to reduce the noise.
Looks like we should have the minimal two patches to queue as fixes
for v2.6.36, then queue the errata flag changes for the upcoming
merge window.
Regards,
Tony
prev parent reply other threads:[~2010-10-04 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 8:18 [PATCH v4 0/4] OMAP2/3: DMA: FIFO drain errata fixes Peter Ujfalusi
2010-10-04 8:18 ` [PATCH v4 1/4] omap: dma: Fix buffering disable bit setting for omap24xx Peter Ujfalusi
2010-10-04 9:14 ` G, Manjunath Kondaiah
2010-10-04 9:50 ` Jarkko Nikula
2010-10-04 8:18 ` [PATCH v4 2/4] OMAP: DMA: Introduce errata handling variable, and macro Peter Ujfalusi
2010-10-04 8:18 ` [PATCH v4 3/4] OMAP2: DMA: Use errata flag for disabling buffering Peter Ujfalusi
2010-10-04 9:15 ` G, Manjunath Kondaiah
2010-10-04 8:18 ` [PATCH v4 4/4] OMAP3: DMA: Errata i541: sDMA FIFO draining does not finish Peter Ujfalusi
2010-10-04 9:17 ` G, Manjunath Kondaiah
2010-10-04 10:42 ` Peter Ujfalusi
2010-10-04 11:04 ` G, Manjunath Kondaiah
2010-10-04 16:55 ` Tony Lindgren
2010-10-04 8:29 ` [PATCH v4 0/4] OMAP2/3: DMA: FIFO drain errata fixes Peter Ujfalusi
2010-10-04 8:33 ` Peter Ujfalusi
2010-10-04 16:57 ` Tony Lindgren [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=20101004165742.GT3117@atomide.com \
--to=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).