From: sourav.poddar@ti•com (Sourav Poddar)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC/PATCH 0/3] arm: omap: patches from -rt
Date: Thu, 1 Aug 2013 22:37:51 +0530 [thread overview]
Message-ID: <51FA95E7.6040602@ti.com> (raw)
In-Reply-To: <1375359165-8411-1-git-send-email-balbi@ti.com>
On Thursday 01 August 2013 05:42 PM, Felipe Balbi wrote:
> Hi,
>
> the next three patches were taken from v3.10.4-rt1 patchset.
>
> I don't have any boards available to test them, so I'd suggest
> testing in as many platforms as possible before pushing
> upstream.
>
> By pushing these patches upstream, we help decrease the amount
> of out-of-tree changes rt folks need to carry.
>
> Frank Rowand (1):
> arm: omap: convert omap boot_lock to raw
>
> Sebastian Andrzej Siewior (1):
> i2c/omap: drop the lock hard irq context
>
> Thomas Gleixner (1):
> serial: omap: fix omap lock crap
>
> arch/arm/mach-omap2/omap-smp.c | 10 +++++-----
> drivers/i2c/busses/i2c-omap.c | 5 +----
> drivers/tty/serial/omap-serial.c | 12 ++++--------
> 3 files changed, 10 insertions(+), 17 deletions(-)
>
Tested this series on
omap4-sdp:
- Boot tested .
- run i2c dump on buses where devices were present.
- check wakeup from suspend.
omap5-uevm:
- Boot tested.
- Tested this series on buses where devices are present.
dra7-evm:
- Boot tested.
- run i2c dump on buses where devices are present.
Tested-by: Sourav Poddar <sourav.poddar@ti•com>
prev parent reply other threads:[~2013-08-01 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 12:12 [RFC/PATCH 0/3] arm: omap: patches from -rt Felipe Balbi
2013-08-01 12:12 ` [RFC/PATCH 1/3] i2c/omap: drop the lock hard irq context Felipe Balbi
2013-08-01 12:12 ` [RFC/PATCH 2/3] serial: omap: fix omap lock crap Felipe Balbi
2013-08-01 12:12 ` [RFC/PATCH 3/3] arm: omap: convert omap boot_lock to raw Felipe Balbi
2013-08-01 13:37 ` Russell King - ARM Linux
2013-08-01 13:48 ` [RFC/PATCH v2] arm: convert arm " Felipe Balbi
2013-08-01 17:07 ` Sourav Poddar [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=51FA95E7.6040602@ti.com \
--to=sourav.poddar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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