public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap@vger.kernel.org
Subject: Re: About to tag v2.6.26-omap1, patch queue deleted, please check and repost
Date: Fri, 8 Aug 2008 13:34:02 +0300	[thread overview]
Message-ID: <20080808103400.GT24923@atomide.com> (raw)
In-Reply-To: <20080808102933.GS24923@atomide.com>

* Tony Lindgren <tony@atomide.com> [080808 13:29]:
> * David Brownell <david-b@pacbell.net> [080808 02:51]:
> > On Thursday 07 August 2008, Tony Lindgren wrote:
> > > 
> > > > Two problems on the OSK5912:
> > > > 
> > > >  - cpufreq oopses on boot
> > > >  - continuous i2c overflow errors
> > > > 
> > > > ISTR both of these bugs are in mainline too.  I'd say the
> > > > I2C regression is higher priority.
> > > 
> > > Hmm, I wonder what has broken I2C?
> > 
> > Seems fixed now; goof in earlier error handling patch.
> > 
> > 
> > > Anyways, let's fix these regressions before tagging.
> > 
> > I've not yet looked at the cpufreq thing, but after
> > applying the patch from Chandra Shekhar the I2C problem
> > went away.
> 
> OK
> 
> > However that still doesn't make OSK happy.  It wedges
> > sometime after freeing init memory ... timer interrupts
> > are no longer happening, the LED stops flashing.  The
> > userspace has sometimes started the watchdog daemon, in
> > which case a watchdog timeout fires and it reboots.
> 
> Hmm could it be the dmtimer posted mode patch applied
> earlier?
> 
> > FWIW mainline fails *really* early, before showing any
> > kernel messages at all.
> 
> Bummer, too bad my osk is also connected to my non-responding remote
> power switch :(
> 
> I'll tag v2.6.26-omap1 despite these issues, we can branch
> and do -omap2 when we have sorted these remaining issues out.

Currently only pushed to kernel.org git tree, looks like
source.mvista.com is down right now.

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-08-08 10:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 14:35 About to tag v2.6.26-omap1, patch queue deleted, please check and repost Tony Lindgren
2008-08-05 15:50 ` Gadiyar, Anand
2008-08-05 18:11   ` Dirk Behme
2008-08-06 13:51     ` arun c
2008-08-06 21:31     ` Josh Karabin
2008-08-06 23:30 ` David Brownell
2008-08-07 10:57   ` Tony Lindgren
2008-08-07 13:43     ` About to tag v2.6.26-omap1, patch queue deleted, please checkand repost shekhar, chandra
2008-08-07 23:50     ` About to tag v2.6.26-omap1, patch queue deleted, please check and repost David Brownell
2008-08-08 10:29       ` Tony Lindgren
2008-08-08 10:34         ` Tony Lindgren [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=20080808103400.GT24923@atomide.com \
    --to=tony@atomide.com \
    --cc=david-b@pacbell.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox