From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>, "H. Anvin" <hpa@zytor.com>,
Matt Mackall <mpm@selenic.com>,
Linux-tiny@selenic.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] x86: Configure out compilation of Simple Boot Flag support
Date: Wed, 13 Feb 2008 11:09:35 +0100 [thread overview]
Message-ID: <20080213110935.28689262@crazy> (raw)
In-Reply-To: <20080213092958.GB25258@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
Le Wed, 13 Feb 2008 10:29:58 +0100,
Ingo Molnar <mingo@elte.hu> a écrit :
> no strong feelings if the ACPI guys ack it - but i suspect the
> renaming of the function from acpi_parse_sbf to sbf_acpi_parse was
> unnecessary?
I rename acpi_parse_sbf() to sbf_acpi_parse() because the function was
moved from arch/x86/kernel/acpi/boot.c, where pretty much all functions
are named acpi_*() to the file arch/x86/kernel/bootflag.c, where all
the functions are named sbf_*(). However, I don't mind reverting that
renaming, I just thought it was cleaner, but I have no strong opinion
on it.
Any thoughts about the duplicate call to
acpi_table_parse(ACPI_SIG_BOOT, acpi_parse_sbf) ?
Thanks for your comments,
Thomas
--
Thomas Petazzoni, Free Electrons
Free Embedded Linux Training Materials
on http://free-electrons.com/training
(More than 1500 pages!)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-02-13 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 8:44 [RFC] [PATCH] x86: Configure out compilation of Simple Boot Flag support Thomas Petazzoni
2008-02-13 9:29 ` Ingo Molnar
2008-02-13 10:09 ` Thomas Petazzoni [this message]
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=20080213110935.28689262@crazy \
--to=thomas.petazzoni@free-electrons.com \
--cc=Linux-tiny@selenic.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=tglx@linutronix.de \
/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