Read and follow Documentation/SubmittingPatches in the Linux Kernel source tree.
Proposed patches to the Linux ACPI kernel sub-system should be e-mailed to firstname.lastname@example.org for review, comment, and testing by the community. Patches that touch code outside drivers/acpi/ must also cc: email@example.com.
It is important to describe your expectations of the patch in the e-mail. If it is an experiment, or a debug patch, please say so. If it works just for you, but you think it is ready to go upstream, please say so. If it has been tested by others and Acked-by: others, please note that also. When you think it is ready to go upstream, be sure to add firstname.lastname@example.org to the "to: list" and include "please apply" in the message.
Note that Len prefers patches in plain text, as that is what reviewers prefer to read. But if you need to use attachments, to prevent your mail client from garbling plain text, he can handle those, too.
Len also takes patches directly from bugzilla entries. Indeed, he tries to give priority to bugzilla fixes because bugzilla does such a good job of remembering the details of the issue, and the people involved have taken the trouble to carefully enter the data in bugzilla.
If you send a patch as an attachment, or attach it to bugzilla, it is helpful if you format the patch according to SubmittingPatches, that is, include a From:, a Subject:, and check-in comments before the patch body, to make it look enough like an e-mail message that git-am can parse it without manual editing.