From: Dan Carpenter <dan.carpenter@oracle.com>
To: Shakthi Kannan <shakthimaan@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Using c2xml on kernel sources
Date: Tue, 20 Mar 2012 13:37:02 +0300 [thread overview]
Message-ID: <20120320103702.GN3163@mwanda> (raw)
In-Reply-To: <CABG-yt06Kw2uFnmrshcHYjgf_cMgzKVdMPe6BXOP2nryhRjBpg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
On Tue, Mar 20, 2012 at 02:30:18PM +0530, Shakthi Kannan wrote:
> Hi,
>
> I would like to run c2xml on the Linux kernel sources. Is there a
> recommended way of using the tool on kernel code?
>
> I tried running it directly on a source file, but, get the
> 'header-file "unable to open" error.
>
> $ c2xml linux-3.0.4/net/ethernet/eth.c
>
make C=2 CHECK="c2xml > foo.xml" net/ethernet/eth.o
regards,
dan carpenter
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-20 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 9:00 Using c2xml on kernel sources Shakthi Kannan
2012-03-20 9:32 ` Bernd Petrovitsch
2012-03-20 10:37 ` Dan Carpenter [this message]
2012-03-20 15:25 ` Shakthi Kannan
2012-03-20 15:40 ` Dan Carpenter
2012-05-23 9:59 ` Shakthi Kannan
2012-05-23 18:30 ` Christopher Li
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=20120320103702.GN3163@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-sparse@vger.kernel.org \
--cc=shakthimaan@gmail.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;
as well as URLs for NNTP newsgroup(s).