Lines Matching refs:release
120 https://github.com/acpica/acpica.git. As a rule, a release is made every
124 Linux, there is a release process to convert the ACPICA git commits into
126 "linuxized ACPICA patches". The release process is carried out on a local
127 copy the ACPICA git repository. Each commit in the monthly release is
129 ACPICA release patchset for the Linux ACPI community. This process is
195 the release process fully automatically.
202 1. Legacy divergences - Before the current ACPICA release process was
208 made directly in the Linux sources obviously hurts the ACPICA release
211 release utilities (please refer to Section 4 below for the details).
218 4. ACPICA release fixups - ACPICA only tests commits using a set of the
222 linuxized ACPICA patches during the release process. When the release
228 respect to the ACPICA release process. If such commits are reverted or
235 This paragraph guides Linux developers to use the ACPICA upstream release
237 before they become available from the ACPICA release process.
259 You can generate the ACPICA release series yourself and rebase your code on
260 top of the generated ACPICA release patches::