mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	fweisbec@gmail.com, heiko.carstens@de.ibm.com,
	tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/urgent] hw-breakpoints: Let modify_user_hw_breakpoint() return an int
Date: Mon, 14 Dec 2009 11:54:35 +0100	[thread overview]
Message-ID: <20091214105435.GA15766@elte.hu> (raw)
In-Reply-To: <20091214213817.dea4fe86.sfr@canb.auug.org.au>


* Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Ingo,
> 
> On Mon, 14 Dec 2009 09:49:44 GMT tip-bot for Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> >
> > Commit-ID:  4983ee49cf0393fd786891dd53af41146cf9f98b
> > Gitweb:     http://git.kernel.org/tip/4983ee49cf0393fd786891dd53af41146cf9f98b
> > Author:     Heiko Carstens <heiko.carstens@de.ibm.com>
> > AuthorDate: Mon, 14 Dec 2009 10:24:12 +0100
> > Committer:  Ingo Molnar <mingo@elte.hu>
> > CommitDate: Mon, 14 Dec 2009 10:42:57 +0100
> > 
> > hw-breakpoints: Let modify_user_hw_breakpoint() return an int
> > 
> > Let modify_user_hw_breakpoint return an int to avoid hundreds of
> > compile warnings like this one:
> > 
> >  include/linux/hw_breakpoint.h: In function 'modify_user_hw_breakpoint':
> >  include/linux/hw_breakpoint.h:96:
> >   warning: return makes integer from pointer without a cast
> > 
> > Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
> > Cc: Frederic Weisbecker <fweisbec@gmail.com>
> > LKML-Reference: <20091214092412.GA5242@osiris.boeblingen.de.ibm.com>
> > Signed-off-by: Ingo Molnar <mingo@elte.hu>
> > ---
> >  include/linux/hw_breakpoint.h |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/include/linux/hw_breakpoint.h b/include/linux/hw_breakpoint.h
> > index 41235c9..3f3ac2f 100644
> > --- a/include/linux/hw_breakpoint.h
> > +++ b/include/linux/hw_breakpoint.h
> > @@ -90,7 +90,7 @@ static inline struct arch_hw_breakpoint *counter_arch_bp(struct perf_event *bp)
> >  static inline struct perf_event *
> >  register_user_hw_breakpoint(struct perf_event_attr *attr,
> >  			    perf_overflow_handler_t triggered,
> > -			    struct task_struct *tsk)	{ return NULL; }
> > +			    struct task_struct *tsk)	{ return 0; }
> >  static inline int
> >  modify_user_hw_breakpoint(struct perf_event *bp,
> >  			  struct perf_event_attr *attr)	{ return -ENOSYS; }
> 
> This applied incorrectly ... it was a fix for modify_user_hw_breakpoint(), 
> but that fix has already bee applied to perf/urgent ...

yeah ... zapped it.

	Ingo

      reply	other threads:[~2009-12-14 10:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14  9:24 [PATCH] hw-breakpoints: let modify_user_hw_breakpoint " Heiko Carstens
2009-12-14  9:49 ` [tip:perf/urgent] hw-breakpoints: Let modify_user_hw_breakpoint() " tip-bot for Heiko Carstens
2009-12-14 10:37   ` Frederic Weisbecker
2009-12-14 10:38   ` Stephen Rothwell
2009-12-14 10:54     ` Ingo Molnar [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=20091214105435.GA15766@elte.hu \
    --to=mingo@elte.hu \
    --cc=fweisbec@gmail.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome