From: Len Brown <lenb@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: rjw@sisk.pl, linaro-dev@lists.linaro.org, patches@linaro.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/4] ACPI / idle: remove unused definition
Date: Fri, 08 Feb 2013 18:35:05 -0500 [thread overview]
Message-ID: <51158BA9.3090804@kernel.org> (raw)
In-Reply-To: <1360017883-9544-1-git-send-email-daniel.lezcano@linaro.org>
series applied.
thanks,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2013-02-08 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 22:44 [PATCH 1/4] ACPI / idle: remove unused definition Daniel Lezcano
2013-02-04 22:44 ` [PATCH 2/4] ACPI / idle : remove pointless headers Daniel Lezcano
2013-02-04 22:44 ` [PATCH 3/4] ACPI / idle: pass the cpuidle_device parameter Daniel Lezcano
2013-02-04 22:44 ` [PATCH 4/4] ACPI / idle: remove usage of the statedata Daniel Lezcano
2013-02-08 23:35 ` Len Brown [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=51158BA9.3090804@kernel.org \
--to=lenb@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).