From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Len Brown <len.brown@intel.com>,
linux-pm@lists.linux-foundation.org,
Lin Ming <ming.m.lin@intel.com>,
"Moore, Robert" <robert.moore@intel.com>
Subject: Re: [Resend][PATCH 0/4] ACPI: Avoid executing _PRW twice for all devices
Date: Mon, 12 Jul 2010 21:35:40 +0200 [thread overview]
Message-ID: <201007122135.40204.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.2.00.1007121434040.25332@localhost.localdomain>
On Monday, July 12, 2010, Len Brown wrote:
>
> > [3/4] - Simplifies code in acpi_ev_initialize_gpe_block(), which only is a
> > cosmetic thing, but worth doing IMO.
>
> FYI, this one had a white-space issue on the line with the "enabled:"
> label -- the patch was missing some tabs and spaces that were in the tree;
> but that was the only problem with it.
>
> > Please apply.
Thanks!
Rafael
prev parent reply other threads:[~2010-07-12 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 22:41 [Resend][PATCH 0/4] ACPI: Avoid executing _PRW twice for all devices Rafael J. Wysocki
2010-07-07 22:42 ` [Resend][PATCH 1/4] ACPI: Fix bogus GPE test in acpi_bus_set_run_wake_flags() Rafael J. Wysocki
2010-07-07 22:43 ` [Resend][PATCH 2/4] ACPI / ACPICA: Do not execute _PRW methods during initialization Rafael J. Wysocki
2010-07-07 22:44 ` [Resend][PATCH 3/4] ACPI / ACPICA: Simplify acpi_ev_initialize_gpe_block() Rafael J. Wysocki
2010-07-07 22:45 ` [Resend][PATCH 4/4] ACPI / ACPICA: Fail acpi_gpe_wakeup() if ACPI_GPE_CAN_WAKE is unset Rafael J. Wysocki
2010-07-12 18:37 ` [Resend][PATCH 0/4] ACPI: Avoid executing _PRW twice for all devices Len Brown
2010-07-12 19:35 ` Rafael J. Wysocki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201007122135.40204.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ming.m.lin@intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=robert.moore@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox