From: Eduardo Valentin <edubezval@gmail.com>
To: Rui Zhang <rui.zhang@intel.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Thermal SoC management updates for v4.8-rc1
Date: Wed, 3 Aug 2016 16:26:42 -0700 [thread overview]
Message-ID: <20160803232638.GA25554@localhost.localdomain> (raw)
In-Reply-To: <1470265127-22631-1-git-send-email-edubezval@gmail.com>
On Wed, Aug 03, 2016 at 03:58:47PM -0700, Eduardo Valentin wrote:
> Hello Rui,
>
> Please pull from
So, forgot to mention that I have been away from upstream work for some
time now, and I am still catching up on my emails.
I've just realized that this may be a bit too late for the pull. I saw
that you had some comments on the thermal subsystem reorg. Let me know
if this pull still causes troubles. We can always post pone to next
merge window.
Let me know how you want to handle this one.
BR,
Eduardo Valentin
next prev parent reply other threads:[~2016-08-03 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 22:58 [GIT PULL] Thermal SoC management updates for v4.8-rc1 Eduardo Valentin
2016-08-03 23:26 ` Eduardo Valentin [this message]
2016-08-04 5:21 ` Zhang Rui
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=20160803232638.GA25554@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@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;
as well as URLs for NNTP newsgroup(s).