From: "Zhenmin Li" <zli4@cs.uiuc.edu>
To: "'Geert Uytterhoeven'" <geert@linux-m68k.org>,
"'Linux/m68k'" <linux-m68k@lists.linux-m68k.org>,
"'Linux/m68k on Mac'" <linux-mac68k@mac.linux-m68k.org>
Cc: "'Linux Kernel Development'" <linux-kernel@vger.kernel.org>
Subject: RE: [OPERA] Potential bugs detected by static analysis tool in 2.6.4
Date: Thu, 6 May 2004 11:44:37 -0500 [thread overview]
Message-ID: <002d01c43389$6bbbea70$76f6ae80@Turandot> (raw)
In-Reply-To: <Pine.GSO.4.58.0405061141290.12096@waterleaf.sonytel.be>
Sorry for the typo. The line number should be 264, and the context is:
if (macintosh_config->adb_type == MAC_ADB_IOP) {
if (macintosh_config->ident == MAC_MODEL_IIFX) {
iop_base[IOP_NUM_ISM] = (struct mac_iop *)
ISM_IOP_BASE_IIFX;
} else {
iop_base[IOP_NUM_ISM] = (struct mac_iop *)
ISM_IOP_BASE_QUADRA;
}
iop_base[IOP_NUM_SCC]->status_ctrl = 0;
iop_ism_present = 1;
}
Thanks,
OPERA Research Group
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Geert Uytterhoeven
Sent: Thursday, May 06, 2004 4:44 AM
To: Linux/m68k; Linux/m68k on Mac
Cc: Zhenmin Li; Linux Kernel Development
Subject: Re: [OPERA] Potential bugs detected by static analysis tool in
2.6.4
On Wed, 5 May 2004, Zhenmin Li wrote:
> We ran our static analysis tool upon Linux 2.6.4 source files, and found
> some potential errors. Since all of them are detected by the tool, we need
> more effort to inspect. We would appreciate your help if anyone can verify
> whether they are bugs or not.
>
> Thanks a lot,
>
> OPERA Research Group
> University of Illinois at Urbana-Champaign
>
>
>
> Version: 2.6.4
[...]
> 8. /arch/m68k/mac/iop.c, Line 164:
Should be line 264?
> iop_base[IOP_NUM_SCC]->status_ctrl = 0;
>
> Maybe change to:
> iop_base[IOP_NUM_ISM]->status_ctrl = 0;
Mac guys, is this correct?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like
that.
-- Linus
Torvalds
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-05-06 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 3:41 [OPERA] Potential bugs detected by static analysis tool in 2.6.4 Zhenmin Li
2004-05-06 9:43 ` Geert Uytterhoeven
2004-05-06 16:29 ` Brad Boyer
2004-05-06 16:44 ` Zhenmin Li [this message]
2004-05-06 20:22 ` Brad Boyer
2004-05-07 0:14 ` Luiz Fernando N. Capitulino
2004-05-07 22:22 ` [OPERA] Another potential error detected by static analysis tool (2.6.4) Zhenmin Li
2004-05-07 23:07 ` Andreas Dilger
[not found] <002701c4331c$092a3b40$76f6ae80@Turandot.suse.lists.linux.kernel>
2004-05-06 7:14 ` [OPERA] Potential bugs detected by static analysis tool in 2.6.4 Andi Kleen
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='002d01c43389$6bbbea70$76f6ae80@Turandot' \
--to=zli4@cs.uiuc.edu \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mac68k@mac.linux-m68k.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