From: Christoph Hellwig <hch@infradead.org>
To: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org, hch@infradead.org,
Prasanna S Panchamukhi <prasanna@in.ibm.com>,
Jim Keniston <jkenisto@us.ibm.com>
Subject: Re: [PATCH] Kprobes: Make kprobe.symbol_name const
Date: Thu, 15 Mar 2007 09:15:01 +0000 [thread overview]
Message-ID: <20070315091501.GA21823@infradead.org> (raw)
In-Reply-To: <20070315043547.GA14236@in.ibm.com>
On Thu, Mar 15, 2007 at 10:05:47AM +0530, Ananth N Mavinakayanahalli wrote:
> From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
>
> Kprobes doesn't scribble the kprobe.symbol_name field. Its only set by
> the module when registering the probe. Modules that exercise good
> hygiene using the "const" qualifier will see warnings...
>
> warning: assignment discards qualifiers from pointer target type
>
> Make struct kprobe.symbol_name const char *
Ok.
prev parent reply other threads:[~2007-03-15 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 4:35 [PATCH] Kprobes: Make kprobe.symbol_name const Ananth N Mavinakayanahalli
2007-03-15 9:15 ` Christoph Hellwig [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=20070315091501.GA21823@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.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