From: Andi Kleen <ak@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ram Pai <linuxram@us.ibm.com>,
agruen@suse.de, akpm@osdl.org, arjan@infradead.org,
bunk@stusta.de, greg@kroah.com, jbeulich@novell.com,
linux-kernel@vger.kernel.org, mathur@us.ibm.com
Subject: Re: [PATCH 4/4] KBUILD: export-symbol usage report generator
Date: Thu, 11 May 2006 16:13:57 +0200 [thread overview]
Message-ID: <200605111613.57718.ak@suse.de> (raw)
In-Reply-To: <20060511134318.GA7667@infradead.org>
> I'd go even further and say every symbol should have a category.
That would be a _lot_ of work. I was thinking more for some specialized
symbols first where the meaning is very clear. Also someone has to
write the infrastructure first.
> These
> catgories than could get labels such as mostly stable
I don't labels like "stable" etc. very much because it would give false
expectations to external users.
-Andi
prev parent reply other threads:[~2006-05-11 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 23:55 [PATCH 4/4] KBUILD: export-symbol usage report generator Ram Pai
2006-05-11 11:43 ` Andi Kleen
2006-05-11 13:43 ` Christoph Hellwig
2006-05-11 14:13 ` Andi Kleen [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=200605111613.57718.ak@suse.de \
--to=ak@suse.de \
--cc=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=mathur@us.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 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.