From: Andi Kleen <ak@suse.de>
To: "Zhenmin Li" <zli4@cs.uiuc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OPERA] Potential bugs detected by static analysis tool in 2.6.4
Date: 06 May 2004 00:14:51 -0700 [thread overview]
Message-ID: <p73ad0mc9hw.fsf@verdi.suse.de> (raw)
In-Reply-To: <002701c4331c$092a3b40$76f6ae80@Turandot.suse.lists.linux.kernel>
"Zhenmin Li" <zli4@cs.uiuc.edu> writes:
> 5. /arch/x86_64/kernel/mpparse.c, Line 652:
> Dprintk("Boot CPU = %d\n", boot_cpu_physical_apicid);
>
> Maybe change to:
> Dprintk("Boot CPU = %d\n", boot_cpu_id);
They are the same anyways:
include/asm-x86_64/acpi.h:144:#define boot_cpu_physical_apicid boot_cpu_id
-Andi
next parent reply other threads:[~2004-05-06 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002701c4331c$092a3b40$76f6ae80@Turandot.suse.lists.linux.kernel>
2004-05-06 7:14 ` Andi Kleen [this message]
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
2004-05-06 20:22 ` Brad Boyer
2004-05-07 0:14 ` Luiz Fernando N. Capitulino
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=p73ad0mc9hw.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zli4@cs.uiuc.edu \
/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