From: Josh Triplett <josh@freedesktop.org>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Change the symbol access list to pseudo list
Date: Tue, 16 Jan 2007 20:43:48 -0800 [thread overview]
Message-ID: <45ADA984.6060509@freedesktop.org> (raw)
In-Reply-To: <20070117023441.GB962@chrisli.org>
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
Christopher Li wrote:
> The pseudo list contain more information. It can
> get to the symbol as well as the usage information.
> Now it is much easier to answer the question like:
> "what function does this functions calls to."
>
> Signed-Off-By: Christopher Li <sparse@chrisli.org>
Good idea. Merged.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-01-17 4:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 2:34 [PATCH] Change the symbol access list to pseudo list Christopher Li
2007-01-17 4:43 ` Josh Triplett [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=45ADA984.6060509@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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;
as well as URLs for NNTP newsgroup(s).