From: liguo zhang <liguo.zhang@mediatek.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: srv_heupstream@mediatek.com,
Matthias Brugger <matthias.bgg@gmail.com>,
Eddie Huang <eddie.huang@mediatek.com>,
Xudong Chen <xudong.chen@mediatek.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/2] Document: i2c: Add a dt binding for mediatek MT2701 soc
Date: Fri, 8 Jan 2016 09:12:08 +0800 [thread overview]
Message-ID: <1452215528.2088.0.camel@mhfsdcap03> (raw)
In-Reply-To: <20160104095511.GB1524@katana>
On Mon, 2016-01-04 at 10:55 +0100, Wolfram Sang wrote:
> On Mon, Jan 04, 2016 at 02:15:37PM +0800, Liguo Zhang wrote:
> > Add a dt binding for the MT2701 soc.
> >
> > Signed-off-by: Liguo Zhang <liguo.zhang@mediatek.com>
>
> This should probably go with the other patch via arm-soc, or?
The patch about i2c dts info for MT2701 depends on the MT2701 clock
patch. After the MT2701 clock patch is accepted, the i2c patch for
MT2701 may be accepted.
The MT2701 clock patch:
http://lists.infradead.org/pipermail/linux-mediatek/2016-January/003489.html
>
> In that case:
>
> Acked-by: Wolfram Sang <wsa@the-dreams.de>
>
next prev parent reply other threads:[~2016-03-07 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 6:15 [PATCH 1/2] Document: i2c: Add a dt binding for mediatek MT2701 soc Liguo Zhang
[not found] ` <1451888138-11471-1-git-send-email-liguo.zhang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2016-01-04 6:15 ` [PATCH 2/2] dts: MT2701: add i2c dts info for MT2701 Liguo Zhang
2016-01-04 9:55 ` [PATCH 1/2] Document: i2c: Add a dt binding for mediatek MT2701 soc Wolfram Sang
2016-01-08 1:12 ` liguo zhang [this message]
2016-01-08 1:12 ` liguo zhang
2016-01-08 7:45 ` Wolfram Sang
2016-02-02 10:50 ` Matthias Brugger
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=1452215528.2088.0.camel@mhfsdcap03 \
--to=liguo.zhang@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=srv_heupstream@mediatek.com \
--cc=wsa@the-dreams.de \
--cc=xudong.chen@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;
as well as URLs for NNTP newsgroup(s).