linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mel Gorman <mel@csn.ul.ie>,
	linuxppc-dev@ozlabs.org, arnd@arndb.de,
	Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: 2.6.29-rc4-git1 build break : cell/spu_profiler.o
Date: Mon, 09 Feb 2009 12:49:19 +0530	[thread overview]
Message-ID: <498FD8F7.8010103@in.ibm.com> (raw)
In-Reply-To: <20090209175043.04889757.sfr@canb.auug.org.au>

Stephen Rothwell wrote:
> See http://patchwork.ozlabs.org/patch/22628/
Thanks Stephen. The above patch fixed this build break.

Regards
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

      reply	other threads:[~2009-02-09  7:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09  6:43 2.6.29-rc4-git1 build break : cell/spu_profiler.o Sachin P. Sant
2009-02-09  6:50 ` Stephen Rothwell
2009-02-09  7:19   ` Sachin P. Sant [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=498FD8F7.8010103@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=arnd@arndb.de \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mel@csn.ul.ie \
    --cc=sfr@canb.auug.org.au \
    /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).