From: Keith Owens <kaos@sgi.com>
To: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
Cc: Paulo Marques <pmarques@grupopie.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
akpm@osdl.org, tony.luck@intel.com,
Systemtap <systemtap@sources.redhat.com>,
Jim Keniston <jkenisto@us.ibm.com>
Subject: Re: [patch 1/2] [BUG]kallsyms_lookup_name should return the text addres
Date: Wed, 11 Jan 2006 10:11:26 +1100 [thread overview]
Message-ID: <18641.1136934686@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Tue, 10 Jan 2006 13:07:37 -0800." <20060110130737.A14197@unix-os.sc.intel.com>
Keshavamurthy Anil S (on Tue, 10 Jan 2006 13:07:37 -0800) wrote:
>On Tue, Jan 10, 2006 at 08:45:02PM +0000, Paulo Marques wrote:
>>
>> This conflicts with a similar patch from Keith Owens earlier this week.
>In fact I was the one who brought this issue to Keith and I missed seeing his
>patch on the mailing list.
>
>> I actually prefer Keith's version as it is the one which solves the bug
>> by changing as least as possible the current behavior.
>That's fine, we can live with Keith's patch.
>As long as the bug is solved, I am happy a man:-)
>
>But my [patch 2/2] speeds up the lookup and that can go in, I think.
>Please ack that patch if you think so.
Your second patch changes the behaviour of kallsyms lookup w.r.t
duplicate symbols.
next prev parent reply other threads:[~2006-01-10 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 20:39 kallsyms_lookup_name should return the text addres Anil S Keshavamurthy
2006-01-10 20:39 ` [patch 1/2] [BUG]kallsyms_lookup_name " Anil S Keshavamurthy
2006-01-10 20:45 ` Paulo Marques
2006-01-10 21:07 ` Keshavamurthy Anil S
2006-01-10 23:11 ` Keith Owens [this message]
2006-01-10 23:29 ` Keshavamurthy Anil S
2006-01-11 0:02 ` Keith Owens
2006-01-11 0:07 ` Randy.Dunlap
2006-01-11 0:23 ` Keith Owens
2006-01-11 0:39 ` Keshavamurthy Anil S
2006-01-11 2:26 ` Frank Ch. Eigler
2006-01-10 20:39 ` [patch 2/2] Link new module to the tail of module list Anil S Keshavamurthy
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=18641.1136934686@ocs3.ocs.com.au \
--to=kaos@sgi.com \
--cc=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
--cc=systemtap@sources.redhat.com \
--cc=tony.luck@intel.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