From: Andrew Morton <akpm@linux-foundation.org>
To: Robert Richter <robert.richter@amd.com>
Cc: jaswinder@kernel.org, mingo@elte.hu, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip] x86: oprofile/op_model_amd.c set return values for op_amd_handle_ibs()
Date: Fri, 31 Jul 2009 13:29:27 -0700 [thread overview]
Message-ID: <20090731132927.88c400cc.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090618144731.GX18016@erda.amd.com>
On Thu, 18 Jun 2009 16:47:31 +0200
Robert Richter <robert.richter@amd.com> wrote:
> On 18.06.09 17:09:27, Jaswinder Singh Rajput wrote:
> >
> > op_amd_handle_ibs() should return 0 when IBS is not present or not defined.
> >
> > Fix compilation warning:
> > CC [M] arch/x86/oprofile/op_model_amd.o
> > arch/x86/oprofile/op_model_amd.c: In function ___op_amd_handle_ibs___:
> > arch/x86/oprofile/op_model_amd.c:217: warning: no return statement in function returning non-void
> >
> > Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> > ---
> > arch/x86/oprofile/op_model_amd.c | 7 +++++--
> > 1 files changed, 5 insertions(+), 2 deletions(-)
>
> Applied to:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git master
>
Something has gone badly wrong. This patch took six weeks to turn up
in linux-next.
Apart from anything else this led me to have to fix something which was
already fixed.
All you guys *saw* that fix and still this didn't prompt anyone to
wonder what had gone wrong.
My fix is better, too. The op_amd_handle_ibs() return value is
ignored, so it should return void.
next prev parent reply other threads:[~2009-07-31 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 11:39 [PATCH -tip] x86: oprofile/op_model_amd.c set return values for op_amd_handle_ibs() Jaswinder Singh Rajput
2009-06-18 14:47 ` Robert Richter
2009-07-31 20:29 ` Andrew Morton [this message]
2009-07-31 21:10 ` Robert Richter
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=20090731132927.88c400cc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.com \
--cc=x86@kernel.org \
/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