From: John Daiker <daikerjohn@gmail.com>
To: apw@canonical.com
Cc: linux-kernel@vger.kernel.org, daikerjohn@gmail.com
Subject: checkpatch.pl stalls on net/decnet/dn_fib.c
Date: Thu, 19 Feb 2009 15:05:50 -0800 [thread overview]
Message-ID: <499DE5CE.3030700@gmail.com> (raw)
Andy,
Was running checkpatch.pl on the entire tree today (because my disk
loves to get thrashed like that...) Found what seems to be a stall/hang
while running checkpatch. I know nothing of the internal workings of
checkpatch.pl, but hope that you're able to sniff this one out!
./scripts/checkpatch.pl --file ./net/decnet/dn_fib.c --debug values=9
types=9 possible=9 attr=9
--snip--
51 > . #define endfor_fib_info() }
51 > EEEEEEEEEEEEEEEEEEEEEEEEENNNEE
51 > _____________________________
<E> <E> <_>WS(
)
52 > .
52 > EEE
52 > __
#define for_nexthops(fi) { int nhsel; const struct dn_fib_nh *nh;\
<E> <E> <_>WS( )
<E> <E> <_>DEFINE(#define for_nexthops,()
<EE> <E> <N>PAREN('(')
<EEN> <N> <_>IDENT(fi)
<EEN> <V> <_>PAREN(')') -> N
<EE> <N> <_>WS( )
<EE> <N> <_>END({)
<EE> <E> <_>WS( )
<EE> <E> <_>DECLARE(int )
<EE> <T> <_>IDENT(nhsel)
<EE> <V> <_>END(;)
<EE> <E> <_>WS( )
<EE> <E> <_>DECLARE(const struct dn_fib_nh *)
<EE> <T> <_>IDENT(nh)
<EE> <V> <_>END(;)
<EE> <E> <_>PRECONT(\
)
53 > . #define for_nexthops(fi) { int nhsel; const struct dn_fib_nh *nh;\
53 > EEEEEEEEEEEEEEEEEEEEEENVVNNEETTTTVVVVVEETTTTTTTTTTTTTTTTTTTTTTTTVVEEE
53 > ____________________________________________________________________
HANGHANGHANGHANG
--snip--
Hope this helps! Let me know if I can assist in debugging at all.
Thanks,
John Daiker
next reply other threads:[~2009-02-19 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 23:05 John Daiker [this message]
2009-02-23 14:53 ` Andy Whitcroft
2009-02-23 15:15 ` Andy Whitcroft
2009-02-24 6:55 ` John Daiker
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=499DE5CE.3030700@gmail.com \
--to=daikerjohn@gmail.com \
--cc=apw@canonical.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
Powered by JetHome