From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: Mars Cheng <mars.cheng@mediatek.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
<devicetree@vger.kernel.org>, <cc.hwang@mediatek.com>,
<wsd_upstream@mediatek.com>, Stephen Boyd <sboyd@codeaurora.org>,
<linux-kernel@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
<linux-mediatek@lists.infradead.org>, <wendell.lin@mediatek.com>
Subject: Re: [PATCH 0/5] Add clk and scpsys support for MT6755
Date: Thu, 17 Aug 2017 10:47:59 +0800 [thread overview]
Message-ID: <1502938079.4027.3.camel@mtksdaap41> (raw)
In-Reply-To: <1502855993.4599.1.camel@mtkswgap22>
On Wed, 2017-08-16 at 11:59 +0800, Mars Cheng wrote:
> Hi Rob, Stephen, Matthias
>
> gentle ping.
>
> Thanks.
>
> On Tue, 2017-08-08 at 16:13 +0800, Mars Cheng wrote:
> > Mars Cheng (3):
> > clk: mediatek: add mt6755 clock ID
> > clk: mediatek: add clk support for MT6755
> > soc: mediatek: add MT6755 scpsys support
Hi Mars,
Sean reworked the scpsys driver to remove code duplication, see:
http://lists.infradead.org/pipermail/linux-mediatek/2017-August/009687.html
http://lists.infradead.org/pipermail/linux-mediatek/2017-August/009820.html
I think current driver will have conflict and can't merge as-is, you'll
need to rebase to Matthias' for-next branch.
Joe.C
next prev parent reply other threads:[~2017-08-17 2:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 8:13 Mars Cheng
2017-08-08 8:13 ` [PATCH v1 3/5] clk: mediatek: add mt6755 clock ID Mars Cheng
2017-08-08 8:13 ` [PATCH v1 4/5] clk: mediatek: add clk support for MT6755 Mars Cheng
2017-08-08 8:13 ` [PATCH v1 5/5] soc: mediatek: add MT6755 scpsys support Mars Cheng
2017-08-16 3:59 ` [PATCH 0/5] Add clk and scpsys support for MT6755 Mars Cheng
2017-08-17 2:47 ` Yingjoe Chen [this message]
2017-08-17 10:19 ` Matthias Brugger
2017-08-19 8:17 ` Mars Cheng
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=1502938079.4027.3.camel@mtksdaap41 \
--to=yingjoe.chen@mediatek.com \
--cc=cc.hwang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mars.cheng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=wendell.lin@mediatek.com \
--cc=wsd_upstream@mediatek.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
Powered by JetHome