From: Matthias Brugger <matthias.bgg@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>, liguo zhang <liguo.zhang@mediatek.com>
Cc: srv_heupstream@mediatek.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: Tue, 2 Feb 2016 11:50:03 +0100 [thread overview]
Message-ID: <56B089DB.5060806@gmail.com> (raw)
In-Reply-To: <20160108074523.GA1523@katana>
On 08/01/16 08:45, Wolfram Sang wrote:
> On Fri, Jan 08, 2016 at 09:12:53AM +0800, liguo zhang wrote:
>> 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.
>
> OK. Still, dts changes go via arm-soc 99% of the cases if there is no
> specific need to go via i2c.
>
No specific need here. I will take it through my branch as soon as the
clock driver is accepted.
Liguo, please poke me on this, when this has happened and you have the
feeling, I forgot about.
prev parent reply other threads:[~2016-02-02 10:50 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
2016-01-08 1:12 ` liguo zhang
2016-01-08 7:45 ` Wolfram Sang
2016-02-02 10:50 ` Matthias Brugger [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=56B089DB.5060806@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=eddie.huang@mediatek.com \
--cc=liguo.zhang@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=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).