From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Rob Landley <rlandley@parallels.com>
Cc: Jesper Juhl <jj@chaosbits.net>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>,
Tejun Heo <tj@kernel.org>, Don Zickus <dzickus@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use sed instead of perl to generate x86/kernel/cpu/capflags.c.
Date: Wed, 19 Jan 2011 12:57:24 +0800 [thread overview]
Message-ID: <20110119045724.GB9903@cr0.nay.redhat.com> (raw)
In-Reply-To: <4D35FEF3.4070001@parallels.com>
On Tue, Jan 18, 2011 at 02:58:27PM -0600, Rob Landley wrote:
>
>From: Rob Landley <rlandley@parallels.com>
>
>Replace perl header file generator with smaller/faster/simpler C version.
>
>Signed-off-by: Rob Landley <rlandley@parallels.com>
Pretty nice!
One small problem below.
>
>I ran the attached test script to compare the output of the C program
>with the output of the perl version for every HZ from 1 to 5000 to make
>sure it was producing the same constants.
>
I think you can use diff to compare the perl output and C output,
with different HZ values.
>+ fprintf(file, "#endif /* __KERNEL_TIMECONST_H */\n");
>+
>+ /* Notice if the disk fills up. */
>+
>+ fflush(stdout);
>+ return ferror(stdout);
Why do you fflush stdout while you are writing to 'file'?
Thanks.
prev parent reply other threads:[~2011-01-19 4:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 19:59 Rob Landley
2011-01-16 20:05 ` Jesper Juhl
2011-01-16 20:30 ` Rob Landley
2011-01-16 20:39 ` Jesper Juhl
2011-01-18 20:58 ` Rob Landley
2011-01-19 4:57 ` Américo Wang [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=20110119045724.GB9903@cr0.nay.redhat.com \
--to=xiyou.wangcong@gmail.com \
--cc=dzickus@redhat.com \
--cc=hpa@zytor.com \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlandley@parallels.com \
--cc=tj@kernel.org \
--cc=yinghai@kernel.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
all inboxes | Powered by JetHome®