public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org
Subject: RE: Open issues after 2.6.38 merge window
Date: Mon, 17 Jan 2011 15:45:37 +0530	[thread overview]
Message-ID: <126c39969c8e98576bfed2b4d28794b3@mail.gmail.com> (raw)
In-Reply-To: <9ba47985064c771620bac3f4fce6a3b0@mail.gmail.com>

Tony,
> -----Original Message-----
> From: Santosh Shilimkar [mailto:santosh.shilimkar@ti.com]
> Sent: Saturday, January 15, 2011 10:50 AM
> To: Tony Lindgren; linux-omap@vger.kernel.org
> Subject: RE: Open issues after 2.6.38 merge window
>
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> > owner@vger.kernel.org] On Behalf Of Tony Lindgren
> > Sent: Saturday, January 15, 2011 1:18 AM
> > To: linux-omap@vger.kernel.org
> > Subject: Open issues after 2.6.38 merge window
> >
> > Hi all,
> >
> > Before I update out master branch, let's try to summarize the
> > open issues after the merge window. Here's a list of issues
> > in omap-fixes-for-linus that I'm aware of:
> >
>
> > - omap4430 es1.0 hangs if L2X0 cache is enabled
> >
> Will have look at this one on Monday
>
I don't see the hang with L2X0 enable on my ES1.0 SDP
with the latest Linus's head.

(Mainline 'e78bf5e6cbe837' + Paul's sync timer fix)

The kernel boots fine.

Regards
Santosh

  reply	other threads:[~2011-01-17 10:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 19:47 Open issues after 2.6.38 merge window Tony Lindgren
2011-01-14 20:24 ` Tony Lindgren
2011-01-14 20:37 ` Jarkko Nikula
2011-01-14 20:54   ` Tony Lindgren
2011-01-14 22:22     ` Nishanth Menon
2011-01-14 20:57 ` David Anders
2011-01-14 23:38   ` Tony Lindgren
2011-01-14 23:59     ` Tony Lindgren
2011-01-14 23:54 ` Thomas Weber
2011-01-15  5:19 ` Santosh Shilimkar
2011-01-17 10:15   ` Santosh Shilimkar [this message]
2011-01-27 18:41     ` Tony Lindgren
2011-01-17 11:37 ` Aaro Koskinen
2011-01-17 11:59   ` Santosh Shilimkar
2011-01-17 12:11     ` Russell King
2011-01-17 12:19       ` Santosh Shilimkar
2011-01-17 12:24         ` Russell King
2011-01-17 18:29           ` Tony Lindgren
2011-01-17 12:22     ` Aaro Koskinen
2011-01-17 12:35       ` Santosh Shilimkar
2011-01-17 12:50         ` Russell King
2011-01-17 18:20           ` Tony Lindgren
2011-01-17 20:31       ` Paul Walmsley
2011-01-17 20:39         ` Russell King
2011-01-17 21:00           ` Paul Walmsley
2011-01-17 21:19             ` Russell King
2011-01-17 22:49               ` Paul Walmsley

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=126c39969c8e98576bfed2b4d28794b3@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox