From: Robert Richter <robert.richter@amd•com>
To: Arnd Bergmann <arnd@arndb•de>
Cc: linux-kernel <linux-kernel@vger•kernel.org>,
linuxppc-dev@ozlabs•org, Paul Mackerras <paulus@samba•org>,
oprofile-list@lists•sourceforge.net, cel <cel@linux•vnet.ibm.com>,
cbe-oss-dev@ozlabs•org
Subject: Re: [Cbe-oss-dev] powerpc/cell/oprofile: fix mutex locking for spu-oprofile
Date: Mon, 13 Oct 2008 17:13:07 +0200 [thread overview]
Message-ID: <20081013151307.GA23557@erda.amd.com> (raw)
In-Reply-To: <200810131653.29631.arnd@arndb.de>
On 13.10.08 16:53:28, Arnd Bergmann wrote:
> On Monday 25 August 2008, Arnd Bergmann wrote:
> > On Monday 25 August 2008, Paul Mackerras wrote:
> > >=20
> > > > Since rc4 is out now, I understand if you feel more comfortable w=
ith
> > > > putting the patch into -next instead of -merge.
> > >=20
> > > Linus has been getting stricter about only putting in fixes for
> > > regressions and serious bugs (see his recent email to Dave Airlie o=
n
> > > LKML for instance). =A0I assume that the corruption is just in the =
data
> > > that is supplied to userspace and doesn't extend to any kernel data
> > > structures.
> >=20
> > That's right, please queue it for -next then.
>=20
> I just realized that this patch never made it into powerpc-next after
> all, neither benh nor paulus version. Whoever is handling it today,
> could you please pull
>=20
> master.kernel.org:/pub/scm/linux/kernel/git/arnd/cell-2.6.git merge
>=20
> to get this commit below. I have rebased it on top of the current
> benh/powerpc/next branch.
All powerpc oprofile patches are in this branch:
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git powerpc-f=
or-paul
Pending patches are:
Carl Love (1):
powerpc/cell/oprofile: fix mutex locking for spu-oprofile
Roel Kluin (1):
powerpc/cell/oprofile: vma_map: fix test on overlay_tbl_offset
Please pull from there.
-Robert
--=20
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd•com
next prev parent reply other threads:[~2008-10-13 15:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 20:01 [PATCH 2/2] Cell OProfile: SPU mutex lock fix, version 4 Carl Love
2008-08-08 13:26 ` Arnd Bergmann
2008-08-08 22:39 ` [PATCH 2/2] Repost " Carl Love
2008-08-09 13:13 ` please pull cell merge branch Arnd Bergmann
2008-08-10 23:17 ` Paul Mackerras
2008-08-11 7:18 ` [Cbe-oss-dev] " Arnd Bergmann
2008-08-11 7:25 ` powerpc/cell/oprofile: fix mutex locking for spu-oprofile Arnd Bergmann
2008-08-20 11:57 ` Robert Richter
2008-08-20 12:05 ` Arnd Bergmann
2008-08-20 12:39 ` Robert Richter
2008-08-20 14:58 ` Carl Love
2008-08-20 12:39 ` Robert Richter
2008-08-20 13:19 ` Arnd Bergmann
2008-08-21 4:21 ` Paul Mackerras
2008-08-21 8:14 ` [Cbe-oss-dev] " Arnd Bergmann
2008-08-21 10:20 ` Michael Ellerman
2008-08-21 14:58 ` Carl Love
2008-08-25 6:31 ` Paul Mackerras
2008-08-25 7:55 ` Arnd Bergmann
2008-10-13 14:53 ` Arnd Bergmann
2008-10-13 15:13 ` Robert Richter [this message]
2008-08-11 7:25 ` powerpc/cell/oprofile: avoid double free of profile buffer Arnd Bergmann
2008-08-19 11:53 ` Robert Richter
2008-08-11 15:34 ` [Cbe-oss-dev] please pull cell merge branch 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=20081013151307.GA23557@erda.amd.com \
--to=robert.richter@amd$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=cbe-oss-dev@ozlabs$(echo .)org \
--cc=cel@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=oprofile-list@lists$(echo .)sourceforge.net \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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