From: "Ph. Marek" <philipp.marek@bmlv.gv.at>
To: alexander.riesen@synopsys.COM
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCHes available] printk() without KERN_ prefixes? (in 2.5.59) (again)
Date: Tue, 4 Feb 2003 11:58:20 +0100 [thread overview]
Message-ID: <200302041158.20607.philipp.marek@bmlv.gv.at> (raw)
In-Reply-To: <20030204104017.GL5239@riesen-pc.gr05.synopsys.com>
> > #ifdef LITTLE_ENDIAN
> > (wptr[(((win + 1)*4)^4)/4] != 0)) {
> > #else
> > (wptr[win + 1] != 0)) {
> > #endif /* LITTLE_ENDIAN */
> > (the braces { and } don't add up in the file).
>
> they do, but your script doesn't use c preprocessor with right flags,
> which it probably should.
>
> The two braces above should be counted as one depending on LITTLE_ENDIAN
> defined.
# wc change_printk.pl
141 268 2361 change_printk.pl
I don't use the preprocessor - after all, which -D should I give? all? none? a
part? So my script just reads the files.
I know that my script could parse the #if's also - but that's a lot of work
with little use.
How about that?
#if defined(FORCE_ERRORS)
if (0) {
#elif !DEBUG
if (kdebug) {
#endif
...
#if !DEBUG || defined(FORCE_ERRORS)
}
#endif
(seen in arch/ia64/sn/io/sn2/pcibr/pcibr_error.c: pcibr_pioerror() )
It's just too complex to look on the #if's and gives not enough advantages.
Regards,
Phil
next prev parent reply other threads:[~2003-02-04 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302031656.h13Gu7lV029203@napali.hpl.hp.com>
2003-02-04 7:36 ` Ph. Marek
[not found] ` <20030204104017.GL5239@riesen-pc.gr05.synopsys.com>
2003-02-04 10:58 ` Ph. Marek [this message]
[not found] ` <15936.25597.385522.451879@napali.hpl.hp.com>
2003-02-05 7:29 ` Ph. Marek
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=200302041158.20607.philipp.marek@bmlv.gv.at \
--to=philipp.marek@bmlv.gv.at \
--cc=alexander.riesen@synopsys.COM \
--cc=linux-kernel@vger.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®