linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Robert Richter <robert.richter@amd.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.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, 25 Aug 2008 09:55:57 +0200	[thread overview]
Message-ID: <200808250955.57638.arnd@arndb.de> (raw)
In-Reply-To: <18610.20951.764057.574721@cargo.ozlabs.ibm.com>

On Monday 25 August 2008, Paul Mackerras wrote:
>=20
> > Since rc4 is out now, I understand if you feel more comfortable with
> > 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 on
> 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.

That's right, please queue it for -next then.

> > Note that the second patch is trivial and fixes an oopsable condition
> > of the kernel, so at least that should still go into 2.6.27.
>=20
> OK, I'll cherry-pick that one for my next batch for Linus.

Thanks,

	Arnd <><

  reply	other threads:[~2008-08-25  7:55 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 [this message]
2008-10-13 14:53                         ` Arnd Bergmann
2008-10-13 15:13                           ` Robert Richter
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=200808250955.57638.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=cel@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=paulus@samba.org \
    --cc=robert.richter@amd.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).