LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Myron Stowe <myron.stowe@hp.com>
To: lenb@kernel.org
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Myron Stowe <myron.stowe@hp.com>
Subject: [PATCH v3 3/3] ACPI: 80 column adherence and spelling fix (no functional change)
Date: Tue, 04 Nov 2008 14:53:05 -0700 [thread overview]
Message-ID: <20081104215305.15214.41345.stgit@bob.kio> (raw)
In-Reply-To: <20081104213732.15214.174.stgit@bob.kio>
Signed-off-by: Myron Stowe <myron.stowe@hp.com>
---
drivers/acpi/processor_core.c | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/acpi/processor_core.c b/drivers/acpi/processor_core.c
index bc332fc..b57b1f0 100644
--- a/drivers/acpi/processor_core.c
+++ b/drivers/acpi/processor_core.c
@@ -595,9 +595,10 @@ static int acpi_processor_get_info(struct acpi_device *device)
}
/*
- * TBD: Synch processor ID (via LAPIC/LSAPIC structures) on SMP.
- * >>> 'acpi_get_processor_id(acpi_id, &id)' in arch/xxx/acpi.c
- */
+ * TBD: Synch processor ID (via LAPIC/LSAPIC structures) on SMP.
+ * >>> 'acpi_get_processor_id(acpi_id, &id)' in
+ * arch/xxx/acpi.c
+ */
pr->acpi_id = object.processor.proc_id;
}
cpu_index = get_cpu_id(pr->handle, device_declaration, pr->acpi_id);
next prev parent reply other threads:[~2008-11-04 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 21:52 [PATCH v3 0/3] ACPI: Fix for supporting > 256 processor declaration limit Myron Stowe
2008-11-04 21:52 ` [PATCH v3 1/3] ACPI: Disambiguate processor declaration type Myron Stowe
2008-11-04 21:53 ` [PATCH v3 2/3] ACPI: Behave uniquely based on processor declaration definition type Myron Stowe
2008-11-04 21:53 ` Myron Stowe [this message]
2008-11-07 1:15 ` [PATCH v3 0/3] ACPI: Fix for supporting > 256 processor declaration limit Len Brown
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=20081104215305.15214.41345.stgit@bob.kio \
--to=myron.stowe@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH v3 3/3] ACPI: 80 column adherence and spelling fix (no functional change)' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).