public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org, Felipe Balbi <felipe.balbi@nokia.com>
Subject: Re: About to tag v2.6.28-omap1 on Friday
Date: Fri, 9 Jan 2009 14:30:43 +0200	[thread overview]
Message-ID: <20090109123041.GO2536@atomide.com> (raw)
In-Reply-To: <20090108100600.GX27566@atomide.com>

* Tony Lindgren <tony@atomide.com> [090108 12:07]:
> * Tony Lindgren <tony@atomide.com> [090107 21:04]:
> > Hi all,
> > 
> > I'm planning to tag v2.6.28-omap1 on Friday. I'll be going through
> > my omap inbox and applying some obvious fixes, but if anybody has
> > new fixes that should go in, please post them ASAP.
> 
> I've also pushed the recent 23 patch clock series from Paul,
> and merged in Kevin's omap-pm-upstream branch. So please give
> the current l-o head some testing on your favorite boards.

OK, I think this is pretty much it for applying patches for now,
or at least I don't seem to have any more fixes in my omap inbox.

Let's give it few days of testing and tag v2.6.28-omap1 on Sunday
if no issues pop up.

I'm wondering if we should apply "[PATCH 3/3] usb: musb: fix null
pointer check in musb_platform_init" as otherwise the system may not
boot.. Felipe, any comments on that?

Regards,

Tony

  reply	other threads:[~2009-01-09 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 19:04 About to tag v2.6.28-omap1 on Friday Tony Lindgren
2009-01-08 10:06 ` Tony Lindgren
2009-01-09 12:30   ` Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-08 10:22 Eero Nurkkala
2009-01-08 11:12 ` Tony Lindgren
2009-01-08 12:12   ` Eero Nurkkala
2009-01-08 12:16     ` 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=20090109123041.GO2536@atomide.com \
    --to=tony@atomide.com \
    --cc=felipe.balbi@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox