From: Shawn Guo <shawnguo@kernel.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Mark Brown <broonie@kernel.org>,
Leonard Crestez <leonard.crestez@nxp.com>,
Marco Franchi <marco.franchi@nxp.com>,
linux-arm-kernel@lists.infradead.org,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the thermal tree with the imx-mxs tree
Date: Wed, 18 Oct 2017 10:19:45 +0800 [thread overview]
Message-ID: <20171018021944.GE18810@dragon> (raw)
In-Reply-To: <1508291246.2746.41.camel@intel.com>
On Wed, Oct 18, 2017 at 09:47:26AM +0800, Zhang Rui wrote:
> Shawn,
>
> https://patchwork.kernel.org/patch/9841191/
> https://patchwork.kernel.org/patch/9841193/
> Should I drop these two dts patches and leave them to you?
Okay, let's do that to avoid the conflict.
Shawn
prev parent reply other threads:[~2017-10-18 2:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 9:17 linux-next: manual merge of the thermal tree with the imx-mxs tree Mark Brown
2017-10-18 1:47 ` Zhang Rui
2017-10-18 2:19 ` Shawn Guo [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=20171018021944.GE18810@dragon \
--to=shawnguo@kernel.org \
--cc=broonie@kernel.org \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marco.franchi@nxp.com \
--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).