public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Banks <gnb@sgi.com>
To: John Levon <levon@movementarian.org>
Cc: Akinobu Mita <amgta@yacht.ocn.ne.jp>,
	Philippe Elie <phil.el@wanadoo.fr>,
	linux-kernel@vger.kernel.org
Subject: Re: [mm patch] oprofile: backtrace operation does not initialized
Date: Fri, 10 Dec 2004 02:27:26 +1100	[thread overview]
Message-ID: <20041209152726.GE6987@sgi.com> (raw)
In-Reply-To: <20041209145519.GA78695@compsoc.man.ac.uk>

On Thu, Dec 09, 2004 at 02:55:19PM +0000, John Levon wrote:
> On Thu, Dec 09, 2004 at 11:53:53PM +0900, Akinobu Mita wrote:
> 
> > Or, It may be better to revert the return type of oprofile_arch_init()
> > from "void" to "int"  to get the result of initialization.
> 
> I've also lost track of why we don't return -ENODEV from the
> arch_init().

I didn't see a good reason for that change either.  Version 0.2
of the callgraph patch had the int return and worked fine.  Let's
go back.

Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.

  reply	other threads:[~2004-12-09 15:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08  9:30 [mm patch] oprofile: backtrace operation does not initialized Akinobu Mita
2004-12-08  9:34 ` Akinobu Mita
2004-12-08 11:13   ` Ingo Molnar
2004-12-08 11:37     ` Akinobu Mita
2004-12-08 16:00 ` John Levon
2004-12-08 22:31   ` Greg Banks
2004-12-08 23:56     ` Philippe Elie
2004-12-09  0:39       ` Greg Banks
2004-12-09  1:46         ` John Levon
2004-12-09  1:50           ` Greg Banks
2004-12-09  2:23             ` John Levon
2004-12-09 14:22             ` Akinobu Mita
2004-12-09 14:53               ` Akinobu Mita
2004-12-09 14:55                 ` John Levon
2004-12-09 15:27                   ` Greg Banks [this message]
2004-12-09 15:23               ` Greg Banks

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=20041209152726.GE6987@sgi.com \
    --to=gnb@sgi.com \
    --cc=amgta@yacht.ocn.ne.jp \
    --cc=levon@movementarian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil.el@wanadoo.fr \
    /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