If you are unable to use git, you can apply the latest consolidated ACPI test branch using a plain patch:
This directory includes patches from the Linux/ACPI git release branch. Len publishes these when he sends a pull request to Linus. If Linus doesn't pull for awhile, this patch tells you what is waiting to go upstream. As soon as Linus pulls, however, this patch becomes a duplicate of what is in Linus' tree and, thus, no longer applies.
The patches are named like this:
The patch above:
- was created on the release branch
- was created sometime after 2.6.15-rc5
- includes ACPICA, up through 20050902
The directory above includes patches from the Linux_ACPI _test_test branch, as well as other topic branches, such as ACPICA, shown below:
Len rarely publishes individual test patches here, because they can now be pulled from the GUI using gitweb: http://www.kernel.org/git/?p=linux/kernel/git/lenb/linux-acpi-2.6.git
Files on ftp.kernel.org are compressed and signed, per http://www.kernel.org/signature.html
If you'd like to verify the signature, import the key by:
gpg --keyserver wwwkeys.pgp.net --recv-keys 0x517D0F0E verify integrity by:
gpg --verify you can skip <sigfile> if it is in the same directory as <sigfile>.
Both test and release patches have a header at the top of the patch, including commit comments to describe what is included in the patch. Note that you can test whether a patch will apply cleanly before you actually apply it:
$ cd my-src/linux/ To test: $ patch --dry-run -Np1 < acpi.patch For real: $ patch -Np1 < acpi.patch