linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: tony@atomide.com, linux-omap@vger.kernel.org, ajay.gupta@ti.com
Subject: Re: omap: Build failure with tip of Linus' tree
Date: Sun, 23 May 2010 10:38:52 +0300	[thread overview]
Message-ID: <20100523073851.GA28900@gandalf> (raw)
In-Reply-To: <20100523001108.GB15859@matterhorn.lan>

On Sun, May 23, 2010 at 03:11:08AM +0300, Amit Kucheria wrote:
> Tony,
> 
> I see the following build failure with the latest tip from Linus. I'm not
> sure if something is yet to be merged for other subsystem trees before -rc1,
> but a patch to fix the build is attached.

FWIw: Acked-by: Felipe Balbi <felipe.balbi@nokia.com>

-- 
balbi

  reply	other threads:[~2010-05-23  7:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-23  0:11 omap: Build failure with tip of Linus' tree Amit Kucheria
2010-05-23  7:38 ` Felipe Balbi [this message]
2010-05-25 22:22 ` 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=20100523073851.GA28900@gandalf \
    --to=me@felipebalbi.com \
    --cc=ajay.gupta@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;
as well as URLs for NNTP newsgroup(s).