From: Thomas Schlichter <thomas.schlichter@web.de>
To: linux-kernel@vger.kernel.org
Subject: [2.6.4-rc2] bogus semicolon behind if()
Date: Tue, 9 Mar 2004 00:14:01 +0100 [thread overview]
Message-ID: <200403090014.03282.thomas.schlichter@web.de> (raw)
Hi,
recently I found a bogus semicolon an if statement. So I was searching for
other possible problems with following command:
find linux-2.6.4-rc2 -name "*.c" -exec grep -Hn "\<if[[:space:]]*(\([^()]\|
([^()]*)\)*)[[:space:]]*;" {} \;
That found following possible problems:
linux-2.6.4-rc2/arch/um/kernel/tt/tracer.c:257: if(WIFEXITED(status)) ;
linux-2.6.4-rc2/arch/i386/kernel/io_apic.c:2200: if (check_nmi_watchdog() <
0);
linux-2.6.4-rc2/arch/i386/kernel/io_apic.c:2224: if (check_nmi_watchdog() <
0);
linux-2.6.4-rc2/drivers/atm/iphase.c:155: if (!desc1) ;
linux-2.6.4-rc2/drivers/net/wan/pc300_drv.c:3664: if (card->chan[i].d.dev);
linux-2.6.4-rc2/drivers/net/tokenring/ibmtr.c:613: else if
(ti->shared_ram_paging == 0xf); /* No paging in adapter */
linux-2.6.4-rc2/drivers/usb/misc/speedtch.c:92:#define DEBUG_ON(x) do { if
(x); } while (0)
linux-2.6.4-rc2/drivers/usb/media/w9968cf.c:3374: if (tuner.tuner != 0);
linux-2.6.4-rc2/drivers/isdn/capi/capiutil.c:438: else if (c <= 0x0f);
linux-2.6.4-rc2/drivers/isdn/hisax/hfc_sx.c:385: if (Read_hfc(cs,
HFCSX_INT_S1));
linux-2.6.4-rc2/drivers/isdn/hisax/hfc_sx.c:415: if (Read_hfc(cs,
HFCSX_INT_S2));
linux-2.6.4-rc2/drivers/isdn/hisax/hfc_sx.c:1290: if (Read_hfc(cs,
HFCSX_INT_S1));
linux-2.6.4-rc2/drivers/isdn/hisax/hfc_pci.c:131: if (Read_hfc(cs,
HFCPCI_INT_S1));
linux-2.6.4-rc2/drivers/isdn/hisax/hfc_pci.c:161: if (Read_hfc(cs,
HFCPCI_INT_S1));
linux-2.6.4-rc2/drivers/isdn/hisax/hfc_pci.c:1543: if (Read_hfc(cs,
HFCPCI_INT_S1));
linux-2.6.4-rc2/drivers/s390/scsi/zfcp_erp.c:2057: if (status ==
ZFCP_ERP_SUCCEEDED) ; /* no further action */
linux-2.6.4-rc2/drivers/scsi/sg.c:356: if (ppos != &filp->f_pos) ; /* FIXME:
Hmm. Seek to the right place, or fail? */
linux-2.6.4-rc2/drivers/scsi/sg.c:514: if (ppos != &filp->f_pos) ; /* FIXME:
Hmm. Seek to the right place, or fail? */
Best regards
Thomas Schlichter
P.S.: Wouldn't it be nice if gcc complained about these mistakes?
next reply other threads:[~2004-03-08 23:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 23:14 Thomas Schlichter [this message]
2004-03-08 23:43 ` [2.6.4-rc2] bogus semicolon behind if() Andreas Schwab
2004-03-08 23:56 ` Thomas Schlichter
2004-03-09 0:29 ` Andrew Morton
2004-03-09 7:01 ` Philippe Elie
2004-03-09 11:08 ` Thomas Schlichter
2004-03-10 6:08 ` Philippe Elie
2004-03-10 16:20 ` Zwane Mwaikambo
2004-03-17 17:20 ` Maciej W. Rozycki
2004-03-17 16:51 ` Maciej W. Rozycki
2004-03-17 18:25 ` Andrew Morton
2004-03-17 18:50 ` Maciej W. Rozycki
2004-03-18 9:46 ` Mikael Pettersson
2004-03-18 9:52 ` Andrew Morton
2004-03-21 3:51 ` Zwane Mwaikambo
2004-03-21 3:55 ` Zwane Mwaikambo
2004-03-19 19:01 ` Thomas Schlichter
2004-03-19 20:30 ` Maciej W. Rozycki
2004-03-19 23:13 ` Thomas Schlichter
2004-03-09 0:33 ` Andrew Morton
2004-03-09 11:09 ` Thomas Schlichter
-- strict thread matches above, loose matches on Subject: below --
2004-03-20 17:04 Mikael Pettersson
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=200403090014.03282.thomas.schlichter@web.de \
--to=thomas.schlichter@web.de \
--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