From: Kevin Hilman <khilman@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Govindraj.R" <govindraj.raja@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH v2 0/3] tty: serial: OMAP: work around broken IP block, driver
Date: Mon, 30 Jan 2012 11:13:34 -0800 [thread overview]
Message-ID: <87ty3drokh.fsf@ti.com> (raw)
In-Reply-To: <20120126024903.31613.24730.stgit@dusk> (Paul Walmsley's message of "Wed, 25 Jan 2012 19:50:32 -0700")
Paul Walmsley <paul@pwsan.com> writes:
> [ This series is targeted for merging during v3.3-rc ]
>
> Hi
>
> Here's an updated version of OMAP serial bugfix series against v3.3-rc1.
> This revision has:
Reviewed-by: Kevin Hilman <khilman@ti.com>
Tested-by: Kevin Hilman <khilman@ti.com>
Tested on 3430/n900, 3530/Overo and 4430/Panda
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] tty: serial: OMAP: work around broken IP block, driver
Date: Mon, 30 Jan 2012 11:13:34 -0800 [thread overview]
Message-ID: <87ty3drokh.fsf@ti.com> (raw)
In-Reply-To: <20120126024903.31613.24730.stgit@dusk> (Paul Walmsley's message of "Wed, 25 Jan 2012 19:50:32 -0700")
Paul Walmsley <paul@pwsan.com> writes:
> [ This series is targeted for merging during v3.3-rc ]
>
> Hi
>
> Here's an updated version of OMAP serial bugfix series against v3.3-rc1.
> This revision has:
Reviewed-by: Kevin Hilman <khilman@ti.com>
Tested-by: Kevin Hilman <khilman@ti.com>
Tested on 3430/n900, 3530/Overo and 4430/Panda
Kevin
next prev parent reply other threads:[~2012-01-30 19:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 2:50 [PATCH v2 0/3] tty: serial: OMAP: work around broken IP block, driver Paul Walmsley
2012-01-26 2:50 ` Paul Walmsley
2012-01-26 2:50 ` [PATCH v2 1/3] tty: serial: OMAP: use a 1-byte RX FIFO threshold in PIO mode Paul Walmsley
2012-01-26 2:50 ` Paul Walmsley
2012-01-26 2:50 ` [PATCH 2/3] tty: serial: OMAP: block idle while the UART is transferring data " Paul Walmsley
2012-01-26 2:50 ` Paul Walmsley
2012-01-26 2:58 ` Paul Walmsley
2012-01-26 2:58 ` Paul Walmsley
2012-01-27 7:23 ` Govindraj
2012-01-27 7:23 ` Govindraj
2012-02-20 12:35 ` Cousson, Benoit
2012-02-20 12:35 ` Cousson, Benoit
2012-02-21 22:02 ` Paul Walmsley
2012-02-21 22:02 ` Paul Walmsley
2012-02-24 14:35 ` Cousson, Benoit
2012-02-24 14:35 ` Cousson, Benoit
2012-02-28 17:13 ` Paul Walmsley
2012-02-28 17:13 ` Paul Walmsley
2012-02-28 17:22 ` [PATCH] tty: serial: OMAP: Fix oops due to NULL pdata in DT boot Cousson, Benoit
2012-02-28 17:22 ` Cousson, Benoit
2012-02-28 17:28 ` Greg KH
2012-02-28 17:28 ` Greg KH
2012-02-28 18:23 ` Kevin Hilman
2012-02-28 18:23 ` Kevin Hilman
2012-01-26 2:50 ` [PATCH v2 3/3] tty: serial: omap-serial: wakeup latency constraint is in microseconds, not milliseconds Paul Walmsley
2012-01-26 2:50 ` Paul Walmsley
2012-01-27 7:19 ` Govindraj
2012-01-27 7:19 ` Govindraj
2012-01-30 19:13 ` Kevin Hilman [this message]
2012-01-30 19:13 ` [PATCH v2 0/3] tty: serial: OMAP: work around broken IP block, driver Kevin Hilman
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=87ty3drokh.fsf@ti.com \
--to=khilman@ti.com \
--cc=alan@linux.intel.com \
--cc=govindraj.raja@ti.com \
--cc=gregkh@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tomi.valkeinen@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.