All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: kprobes: get rid of distinct type warning
Date: Mon, 21 Dec 2009 16:47:59 +0530	[thread overview]
Message-ID: <20091221111759.GA12670@in.ibm.com> (raw)
In-Reply-To: <20091221101549.GA3850@osiris.boeblingen.de.ibm.com>

On Mon, Dec 21, 2009 at 11:15:49AM +0100, Heiko Carstens wrote:
> From: Heiko Carstens <heiko.carstens@de.ibm.com>
> 
> Every time I see this:
> 
> kernel/kprobes.c: In function 'register_kretprobe':
> kernel/kprobes.c:1038: warning: comparison of distinct pointer types lacks a cast
> 
> I'm wondering if something changed in common code and we need to do
> something for s390. Apparently that's not the case.
> Let's get rid of this annoying warning.
> 
> Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>

Acked-by: Ananth N Mavinakayanahalli <ananth@in.ibm.com>

Thanks Heiko. I'd tested this on x86 and powerpc and neither throws the
warning. No wonder I missed it.

  reply	other threads:[~2009-12-21 11:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 10:15 kprobes: get rid of distinct type warning Heiko Carstens
2009-12-21 11:17 ` Ananth N Mavinakayanahalli [this message]
2009-12-21 12:02   ` Heiko Carstens
2009-12-28 10:08     ` [tip:perf/urgent] kprobes: Fix " tip-bot for Heiko Carstens
2009-12-30 21:29     ` kprobes: get rid of " Andrew Morton
2010-01-04 15:57       ` Heiko Carstens
2010-01-04 22:45         ` Rusty Russell
2010-01-05  8:40           ` Heiko Carstens
2010-01-09  0:18             ` Andrew Morton
2010-01-09 17:45               ` Heiko Carstens

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=20091221111759.GA12670@in.ibm.com \
    --to=ananth@in.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.