From: Len Brown <lenb@kernel.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI: fix mutex names
Date: Fri, 20 Jun 2008 15:03:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0806201503170.3027@localhost.localdomain> (raw)
In-Reply-To: <20080620115656.GA17426@damson.getinternet.no>
looks good.
CONFIG_ACPI_DEBUG=y thanks you.
-Len
On Fri, 20 Jun 2008, Vegard Nossum wrote:
> Hi,
>
> I came across this as I was looking at Ingo's report. This looks correct,
> yeah? (The alternative is to switch the #defines around, but that has
> more serious implications than changing just what is displayed on the
> screen!)
>
>
> Vegard
>
>
> From: Vegard Nossum <vegard.nossum@gmail.com>
> Date: Fri, 20 Jun 2008 13:49:22 +0200
> Subject: [PATCH] ACPI: fix mutex names
>
> This patch reorders the mutex names to match the preceding #defines
> and comment:
>
> /*
> * NOTE: any changes here must be reflected in the acpi_gbl_mutex_names
> * table below also!
> */
> #define ACPI_MTX_INTERPRETER 0 /* AML Interpreter, main lock */
> #define ACPI_MTX_NAMESPACE 1 /* ACPI Namespace */
> #define ACPI_MTX_TABLES 2 /* Data for ACPI tables */
>
> Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
> ---
> include/acpi/aclocal.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/acpi/aclocal.h b/include/acpi/aclocal.h
> index c5cdc32..62d7468 100644
> --- a/include/acpi/aclocal.h
> +++ b/include/acpi/aclocal.h
> @@ -98,8 +98,8 @@ union acpi_parse_object;
>
> static char *acpi_gbl_mutex_names[ACPI_NUM_MUTEX] = {
> "ACPI_MTX_Interpreter",
> - "ACPI_MTX_Tables",
> "ACPI_MTX_Namespace",
> + "ACPI_MTX_Tables",
> "ACPI_MTX_Events",
> "ACPI_MTX_Caches",
> "ACPI_MTX_Memory",
> --
> 1.5.4.1
>
prev parent reply other threads:[~2008-06-20 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 11:56 [PATCH] ACPI: fix mutex names Vegard Nossum
2008-06-20 19:03 ` Len Brown [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=alpine.LFD.1.10.0806201503170.3027@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/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