All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Woodruff, Richard" <r-woodruff2@ti.com>,
	"Ghorai, Sukumar" <s-ghorai@ti.com>
Subject: Re: [PATCH 1/9] omap3/4: uart: fix full-fifo write abort
Date: Mon, 22 Feb 2010 15:07:12 -0800	[thread overview]
Message-ID: <20100222230712.GB18786@atomide.com> (raw)
In-Reply-To: <20100222213932.GW18786@atomide.com>

* Tony Lindgren <tony@atomide.com> [100222 13:35]:
> * Shilimkar, Santosh <santosh.shilimkar@ti.com> [100218 21:22]:
> > Bye the way just to add bit more clarity, this patch addresses TX
> > hardware restriction in the new UART IP used on omap3630 and omap4430.
> > First part of the fix for RX is already in mainline,
> > Commit: "ce13d4716a276f4331d78ba28a5093a63822ab95"
> > 
> > More details on this thread are here.
> > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg19447.html
> 
> Thanks, I've updated the comments for this patch with the link above
> and added the whole series into omap for-next.

Except patches 8 and 9 as they break compile for mach-omap1
and need to be updated.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] omap3/4: uart: fix full-fifo write abort
Date: Mon, 22 Feb 2010 15:07:12 -0800	[thread overview]
Message-ID: <20100222230712.GB18786@atomide.com> (raw)
In-Reply-To: <20100222213932.GW18786@atomide.com>

* Tony Lindgren <tony@atomide.com> [100222 13:35]:
> * Shilimkar, Santosh <santosh.shilimkar@ti.com> [100218 21:22]:
> > Bye the way just to add bit more clarity, this patch addresses TX
> > hardware restriction in the new UART IP used on omap3630 and omap4430.
> > First part of the fix for RX is already in mainline,
> > Commit: "ce13d4716a276f4331d78ba28a5093a63822ab95"
> > 
> > More details on this thread are here.
> > http://www.mail-archive.com/linux-omap at vger.kernel.org/msg19447.html
> 
> Thanks, I've updated the comments for this patch with the link above
> and added the whole series into omap for-next.

Except patches 8 and 9 as they break compile for mach-omap1
and need to be updated.

Regards,

Tony

  reply	other threads:[~2010-02-22 23:06 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18  8:59 [PATCH 1/9] omap3/4: uart: fix full-fifo write abort Santosh Shilimkar
2010-02-18  8:59 ` Santosh Shilimkar
2010-02-18  8:59 ` [PATCH 2/9] omap2/3/4: ioremap omap_globals module Santosh Shilimkar
2010-02-18  8:59   ` Santosh Shilimkar
2010-02-18  8:59   ` [PATCH 3/9] omap4: sdma: Enable the idle modes on omap4 Santosh Shilimkar
2010-02-18  8:59     ` Santosh Shilimkar
2010-02-18  8:59     ` [PATCH 4/9] omap: sdma: Limit the secure reserve channel fix for omap3 Santosh Shilimkar
2010-02-18  8:59       ` Santosh Shilimkar
2010-02-18  8:59       ` [PATCH 5/9] omap4: Fix omap_type() for omap4 Santosh Shilimkar
2010-02-18  8:59         ` Santosh Shilimkar
2010-02-18  8:59         ` [PATCH 6/9] omap3/4: Remove overlapping mapping of L4_WKUP io space Santosh Shilimkar
2010-02-18  8:59           ` Santosh Shilimkar
2010-02-18  8:59           ` [PATCH 7/9] omap4: Add auto-generated irq and dma headers Santosh Shilimkar
2010-02-18  8:59             ` Santosh Shilimkar
2010-02-18  8:59             ` [PATCH 8/9] omap4: Use dma line defines from dma-44xx.h Santosh Shilimkar
2010-02-18  8:59               ` Santosh Shilimkar
2010-02-18  8:59               ` [PATCH 9/9] omap4: Use irq line defines from irq-44xx.h Santosh Shilimkar
2010-02-18  8:59                 ` Santosh Shilimkar
2010-02-22 22:13               ` [PATCH 8/9] omap4: Use dma line defines from dma-44xx.h Tony Lindgren
2010-02-22 22:13                 ` Tony Lindgren
2010-02-18 17:23             ` [PATCH 7/9] omap4: Add auto-generated irq and dma headers Paul Walmsley
2010-02-18 17:23               ` Paul Walmsley
2010-02-18 17:33               ` Shilimkar, Santosh
2010-02-18 17:33                 ` Shilimkar, Santosh
2010-02-19  5:10               ` Shilimkar, Santosh
2010-02-19  5:10                 ` Shilimkar, Santosh
2010-02-18 17:35   ` [PATCH 2/9] omap2/3/4: ioremap omap_globals module Paul Walmsley
2010-02-18 17:35     ` Paul Walmsley
2010-02-18 22:24   ` Kevin Hilman
2010-02-18 22:24     ` Kevin Hilman
2010-02-19  5:13     ` Shilimkar, Santosh
2010-02-19  5:13       ` Shilimkar, Santosh
2010-02-19  5:25 ` [PATCH 1/9] omap3/4: uart: fix full-fifo write abort Shilimkar, Santosh
2010-02-19  5:25   ` Shilimkar, Santosh
2010-02-22 21:39   ` Tony Lindgren
2010-02-22 21:39     ` Tony Lindgren
2010-02-22 23:07     ` Tony Lindgren [this message]
2010-02-22 23:07       ` Tony Lindgren
2010-02-23  5:42       ` Shilimkar, Santosh
2010-02-23  5:42         ` Shilimkar, Santosh
2010-02-23  7:19       ` Shilimkar, Santosh
2010-02-23  7:19         ` Shilimkar, Santosh
2010-02-23 23:12         ` Tony Lindgren
2010-02-23 23:12           ` Tony Lindgren
2010-02-24  4:09           ` Shilimkar, Santosh
2010-02-24  4:09             ` Shilimkar, Santosh
2010-02-23 16:17     ` Shilimkar, Santosh
2010-02-23 16:17       ` Shilimkar, Santosh
2010-02-23 18:54       ` Tony Lindgren
2010-02-23 18:54         ` Tony Lindgren

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=20100222230712.GB18786@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=r-woodruff2@ti.com \
    --cc=s-ghorai@ti.com \
    --cc=santosh.shilimkar@ti.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.