linux-kernel - [PATCH v3 0/3] ACPI: Fix for supporting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081104213732.15214.174.stgit@bob.kio>
Date:	Tue, 04 Nov 2008 14:52:50 -0700
From:	Myron Stowe <myron.stowe@...com>
To:	lenb@...nel.org
Cc:	aystarik@...il.com, yakui.zhao@...el.com, myron.stowe@...com,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH v3 0/3] ACPI: Fix for supporting > 256 processor declaration
	limit

The following three item patch series fixes an issue with the introduction
of > 256 processor declaration support: "Allow processor to be declared with
the Device() instead of Processor()" (git SHA 11bf04c4).

This version, v3, has no functional changes from the original
(gmane.linux.acpi.devel/34815).  The changes, based on reviewer comments, are:
  . a change to the printk verbage (v2),
  . some additional comments (v2),
  . augment an existing printk to aid detection of faulty FW (v3).

Please queue as .29 material.

Thanks,
Myron

---

Myron Stowe (3):
      ACPI: 80 column adherence and spelling fix (no functional change)
      ACPI: Behave uniquely based on processor declaration definition type
      ACPI: Disambiguate processor declaration type

 drivers/acpi/processor_core.c |   86 +++++++++++++++++++++++------------------
 drivers/acpi/scan.c           |    2 -
 include/acpi/acpi_drivers.h   |    1 
 3 files changed, 51 insertions(+), 38 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/