From: Eduardo Valentin <edubezval@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: linux-next: please clean up the thermal-soc tree
Date: Mon, 5 Sep 2016 06:03:35 -0700 [thread overview]
Message-ID: <20160905130333.GA21673@localhost.localdomain> (raw)
In-Reply-To: <20160822114346.4cb45ec5@canb.auug.org.au>
Stephen,
On Mon, Aug 22, 2016 at 11:43:46AM +1000, Stephen Rothwell wrote:
> Hi Eduardo,
>
> The thermal-soc tree now shares quite a few patches (but not commits)
> with the thermal tree. These are causing a few unnecessary conflicts,
> so please clean it up.
I had to be out for several weeks and my tree was broken during this
time causing the above problem. Sorry for this.
I have removed the problematic patches out of linux-next way.
Let me know if you still have troubles.
BR,
Eduardo Valentin
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2016-09-05 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 1:43 linux-next: please clean up the thermal-soc tree Stephen Rothwell
2016-09-05 13:03 ` Eduardo Valentin [this message]
2016-09-05 23:34 ` Stephen Rothwell
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=20160905130333.GA21673@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sfr@canb.auug.org.au \
/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).