Commit bf4f5bf1 authored by Cao jin's avatar Cao jin Committed by Rafael J. Wysocki

ACPI / doc: linuxized-acpica.txt: fix typos

Fix some typos in the linuxized-acpica.txt document.
Signed-off-by: default avatarCao jin <caoj.fnst@cn.fujitsu.com>
[ rjw: Subject / changelog ]
Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
parent 4f7d029b
...@@ -24,7 +24,7 @@ upstream. ...@@ -24,7 +24,7 @@ upstream.
The homepage of ACPICA project is: www.acpica.org, it is maintained and The homepage of ACPICA project is: www.acpica.org, it is maintained and
supported by Intel Corporation. supported by Intel Corporation.
The following figure depicts the Linux ACPI subystem where the ACPICA The following figure depicts the Linux ACPI subsystem where the ACPICA
adaptation is included: adaptation is included:
+---------------------------------------------------------+ +---------------------------------------------------------+
...@@ -110,7 +110,7 @@ upstream. ...@@ -110,7 +110,7 @@ upstream.
Linux patches. The patches generated by this process are referred to as Linux patches. The patches generated by this process are referred to as
"linuxized ACPICA patches". The release process is carried out on a local "linuxized ACPICA patches". The release process is carried out on a local
copy the ACPICA git repository. Each commit in the monthly release is copy the ACPICA git repository. Each commit in the monthly release is
converted into a linuxized ACPICA patch. Together, they form the montly converted into a linuxized ACPICA patch. Together, they form the monthly
ACPICA release patchset for the Linux ACPI community. This process is ACPICA release patchset for the Linux ACPI community. This process is
illustrated in the following figure: illustrated in the following figure:
...@@ -165,7 +165,7 @@ upstream. ...@@ -165,7 +165,7 @@ upstream.
<http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git>. <http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git>.
Before the linuxized ACPICA patches are sent to the Linux ACPI community Before the linuxized ACPICA patches are sent to the Linux ACPI community
for review, there is a quality ensurance build test process to reduce for review, there is a quality assurance build test process to reduce
porting issues. Currently this build process only takes care of the porting issues. Currently this build process only takes care of the
following kernel configuration options: following kernel configuration options:
CONFIG_ACPI/CONFIG_ACPI_DEBUG/CONFIG_ACPI_DEBUGGER CONFIG_ACPI/CONFIG_ACPI_DEBUG/CONFIG_ACPI_DEBUGGER
...@@ -195,12 +195,12 @@ upstream. ...@@ -195,12 +195,12 @@ upstream.
release utilities (please refer to Section 4 below for the details). release utilities (please refer to Section 4 below for the details).
3. Linux specific features - Sometimes it's impossible to use the 3. Linux specific features - Sometimes it's impossible to use the
current ACPICA APIs to implement features required by the Linux kernel, current ACPICA APIs to implement features required by the Linux kernel,
so Linux developers occasionaly have to change ACPICA code directly. so Linux developers occasionally have to change ACPICA code directly.
Those changes may not be acceptable by ACPICA upstream and in such cases Those changes may not be acceptable by ACPICA upstream and in such cases
they are left as committed ACPICA divergences unless the ACPICA side can they are left as committed ACPICA divergences unless the ACPICA side can
implement new mechanisms as replacements for them. implement new mechanisms as replacements for them.
4. ACPICA release fixups - ACPICA only tests commits using a set of the 4. ACPICA release fixups - ACPICA only tests commits using a set of the
user space simulation utilies, thus the linuxized ACPICA patches may user space simulation utilities, thus the linuxized ACPICA patches may
break the Linux kernel, leaving us build/boot failures. In order to break the Linux kernel, leaving us build/boot failures. In order to
avoid breaking Linux bisection, fixes are applied directly to the avoid breaking Linux bisection, fixes are applied directly to the
linuxized ACPICA patches during the release process. When the release linuxized ACPICA patches during the release process. When the release
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment