From: Arjan van de Ven <arjan@infradead.org>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: Matthew Wilcox <matthew@wil.cx>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: some numbers on macros
Date: Sat, 24 May 2008 16:46:15 -0700 [thread overview]
Message-ID: <20080524164615.0ed80f85@infradead.org> (raw)
In-Reply-To: <200805250141.09195.m.kozlowski@tuxland.pl>
On Sun, 25 May 2008 01:41:09 +0200
Mariusz Kozlowski <m.kozlowski@tuxland.pl> wrote:
>
> Interesting part would be to write a 'parser' that actually sees the
> context and understands cpp directives, that could 'walk' the tree.
you could approach it from the opposite angle... I mean, lxr.linux.no
already has all this data in some database.. maybe you can turn it into
a set of database queries ;)
next prev parent reply other threads:[~2008-05-24 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-24 15:48 some numbers on macros Mariusz Kozlowski
2008-05-24 16:33 ` Arjan van de Ven
2008-05-24 18:52 ` Matthew Wilcox
2008-05-24 23:41 ` Mariusz Kozlowski
2008-05-24 23:46 ` Arjan van de Ven [this message]
2008-05-25 9:11 ` Mariusz Kozlowski
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=20080524164615.0ed80f85@infradead.org \
--to=arjan@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=matthew@wil.cx \
/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