From: Mikael Pettersson <mikpe@it.uu.se>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ingo Molnar <mingo@elte.hu>, Chuck Ebbert <cebbert@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: PIC, L-APIC and I/O APIC debug information
Date: Mon, 21 Jul 2008 02:36:40 +0200 [thread overview]
Message-ID: <18563.55832.673541.202465@harpo.it.uu.se> (raw)
In-Reply-To: <Pine.LNX.4.55.0807202226310.24038@cliff.in.clinika.pl>
Maciej W. Rozycki writes:
> Dump all the PIC, local APIC and I/O APIC information at the
> fs_initcall() level, which is after ACPI (if used) has initialised PCI
> information, making the point of invocation consistent across MP-table and
> ACPI platforms. Remove explicit calls to print_IO_APIC() from elsewhere.
> Make the interface of all the functions involved consistent between 32-bit
> and 64-bit versions and make them all static by default by the means of a
> New-and-Improved(TM) __apicdebuginit() macro.
...
> +#define __apicdebuginit(type) static type __init
...
> -void __init print_IO_APIC(void)
> +
> +__apicdebuginit(void) print_IO_APIC(void)
> {
I _really_ dislike how this abuses the C macro preprocessor
to create pointless new syntax.
Since you're editing these function definitions anyway why
not just spell out "static void __init" in readable proper C?
/Mikael
next prev parent reply other threads:[~2008-07-21 0:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 23:52 Maciej W. Rozycki
2008-07-21 0:36 ` Mikael Pettersson [this message]
2008-07-21 11:31 ` Maciej W. Rozycki
2008-07-21 14:04 ` Mikael Pettersson
2008-07-23 0:10 ` Maciej W. Rozycki
2008-07-24 10:37 ` Ingo Molnar
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=18563.55832.673541.202465@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=x86@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®