All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Subject: Open issues after 2.6.38 merge window
Date: Fri, 14 Jan 2011 11:47:58 -0800	[thread overview]
Message-ID: <20110114194758.GM4957@atomide.com> (raw)

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:

- NFS root oopses while mounting root

- omap4430 es1.0 hangs if L2X0 cache is enabled

- omap4 panda powers down after boot (watchdog?)

- omap3 ldp board powers down after boot?

Any other issues?

Regards,

Tony

             reply	other threads:[~2011-01-14 19:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 19:47 Tony Lindgren [this message]
2011-01-14 20:24 ` Open issues after 2.6.38 merge window 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
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=20110114194758.GM4957@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.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 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.