From: Robert Richter <robert.richter@amd.com>
To: Carl Love <cel@us.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@ozlabs.org, cel <cel@linux.vnet.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
oprofile-list@lists.sourceforge.net,
cbe-oss-dev <cbe-oss-dev@ozlabs.org>
Subject: Re: [Patch 0/3] Overview, OProfile SPU event profiling support for IBM Cell processor
Date: Mon, 12 Jan 2009 18:52:44 +0100 [thread overview]
Message-ID: <20090112175244.GJ15411@erda.amd.com> (raw)
In-Reply-To: <1231776927.6621.112.camel@carll-linux-desktop>
On 12.01.09 08:15:27, Carl Love wrote:
>
> On Sun, 2009-01-11 at 10:31 +1100, Benjamin Herrenschmidt wrote:
> > On Thu, 2009-01-08 at 16:26 -0800, Carl Love wrote:
> > > I pulled down the git tree, compiled and installed it. I tested it
> > > against the OProfile testsuite, which includes SPU event profiling
> > > tests. Everything passed. The patch I submitted was against a 2.6.26
> > > tree. You are now on a 2.6.28 tree so perhaps that is why the patch did
> > > not apply cleanly. The patch has been out there for some time.
> >
> > When you submited it on Dec 2, it should have been against whatever was
> > the latest upstream at the time, not 2.6.26.
> >
> > Cheers,
> > Ben.
>
> Ben, Arnd and Robert:
>
> The patch was against the latest Arnd Cell Kernel tree at the time it
> was posted. The OProfile for cell patches have all been submitted,
> accepted by Arnd (CELL Kernel maintainer) and pushed up stream by Arnd.
> Arnd has waited for the OProfile maintainer to review and approve the
> change before Arnd would push it upstream.
The patches are already upstream in v2.6.29-rc1. Hope this is ok. I
had added them to the oprofile tree and the tree was merged be Linus.
-Robert
> So, at this point, Robert's (OProfile kernel maintainer) and Maynard's
> (OProfile user space maintainer) approval for the patches.
>
> The question now goes to Arnd and Robert, who is going to push the
> patches upstream? Looks like Robert is ready to do it, so Arnd do you
> approve the patches? Would you like to have Robert push the patches
> upstream or would you prefer to do it? I think we need an
> answer/agreement on this.
Arnd, I thought the patches were ok for you. If there are still some
concerns, we have to make delta patches.
See also here:
git log -4 -p 25006644e6042aab4bb7cdc4bfc5777cd3141df7
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
next prev parent reply other threads:[~2009-01-12 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 0:18 [Patch 0/3] Overview, OProfile SPU event profiling support for IBM Cell processor Carl Love
2009-01-08 15:48 ` Robert Richter
2009-01-09 0:26 ` Carl Love
2009-01-09 14:30 ` Robert Richter
2009-01-10 23:31 ` Benjamin Herrenschmidt
2009-01-12 16:15 ` Carl Love
2009-01-12 17:52 ` Robert Richter [this message]
2009-01-12 17:59 ` Arnd Bergmann
2009-01-12 18:10 ` Carl Love
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=20090112175244.GJ15411@erda.amd.com \
--to=robert.richter@amd.com \
--cc=benh@kernel.crashing.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=cel@linux.vnet.ibm.com \
--cc=cel@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=oprofile-list@lists.sourceforge.net \
/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