All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Subject: Git tree updated to v2.6.27, some issues remain
Date: Fri, 10 Oct 2008 15:04:29 +0300	[thread overview]
Message-ID: <20081010120427.GZ3044@atomide.com> (raw)

Hi all,

I've just updated our git tree to v2.6.27 and pushed some recent fixes.

Let's try to get the pending issues sorted out and then tag -omap1
at the end of next week. So far it looks like we still have the following
issues remaining:

- i2c transfers not working because of i2c-omap.c PM (These also make
  musb init fail at least on 3430sdp)

- 24xx/34xx write posting issue

- 34xx spurious interrupts about 1/20 reboots

Anything else not working right now?

BTW, I'll out of town for the weekend, then flying back to home on
Monday, so I'll be offline for most part until Tuesday.

Tony

             reply	other threads:[~2008-10-10 12:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 12:04 Tony Lindgren [this message]
2008-10-10 15:43 ` Git tree updated to v2.6.27, some issues remain David Brownell
2008-10-10 15:57   ` Steve Sakoman
2008-10-10 20:49     ` Pandita, Vikram
2008-10-10 22:15       ` Pandita, Vikram
2008-10-10 22:28         ` Pandita, Vikram
2008-10-10 22:54           ` David Brownell
2008-10-10 22:57             ` Pandita, Vikram
2008-10-11  0:32               ` David Brownell
2008-10-11  1:17                 ` Pandita, Vikram
2008-10-11  1:26                   ` David Brownell
2008-10-10 22:29         ` Nathan Monson
2008-10-10 22:34           ` Pandita, Vikram
2008-10-16 19:43 ` David Brownell
2008-10-16 20:00   ` Koen Kooi
2008-10-16 20:46     ` David Brownell
2008-10-17  9:54       ` Felipe Balbi
2008-10-16 21:42   ` Nathan Monson
2008-10-16 22:07     ` David Brownell
2008-10-17  0:19   ` 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=20081010120427.GZ3044@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.