From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND 2/2] arm64: dts: Add dts files for Hisilicon Hi3660 SoC
Date: Thu, 5 Jan 2017 09:40:45 +0000 [thread overview]
Message-ID: <20170105094045.GA679@arm.com> (raw)
In-Reply-To: <586DBD68.7090509@hisilicon.com>
On Thu, Jan 05, 2017 at 11:28:40AM +0800, Chen Feng wrote:
> Could you help review this part?
It would be better if one of the devicetree maintainers reviewed it, but
they're stretched pretty thinly so you might need to sit tight.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Chen Feng <puck.chen@hisilicon.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
xuyiping@hisilicon.com, catalin.marinas@arm.com,
suzhuangluan@hisilicon.com, linux-kernel@vger.kernel.org,
xuwei5@hisilicon.com, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND 2/2] arm64: dts: Add dts files for Hisilicon Hi3660 SoC
Date: Thu, 5 Jan 2017 09:40:45 +0000 [thread overview]
Message-ID: <20170105094045.GA679@arm.com> (raw)
In-Reply-To: <586DBD68.7090509@hisilicon.com>
On Thu, Jan 05, 2017 at 11:28:40AM +0800, Chen Feng wrote:
> Could you help review this part?
It would be better if one of the devicetree maintainers reviewed it, but
they're stretched pretty thinly so you might need to sit tight.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Chen Feng <puck.chen@hisilicon.com>
Cc: xuwei5@hisilicon.com, robh+dt@kernel.org, mark.rutland@arm.com,
catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
suzhuangluan@hisilicon.com, xuyiping@hisilicon.com
Subject: Re: [RESEND 2/2] arm64: dts: Add dts files for Hisilicon Hi3660 SoC
Date: Thu, 5 Jan 2017 09:40:45 +0000 [thread overview]
Message-ID: <20170105094045.GA679@arm.com> (raw)
In-Reply-To: <586DBD68.7090509@hisilicon.com>
On Thu, Jan 05, 2017 at 11:28:40AM +0800, Chen Feng wrote:
> Could you help review this part?
It would be better if one of the devicetree maintainers reviewed it, but
they're stretched pretty thinly so you might need to sit tight.
Will
next prev parent reply other threads:[~2017-01-05 9:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 9:36 [RESEND 1/2] document: dt: add binding for Hi3660 SoC Chen Feng
2016-12-26 9:36 ` Chen Feng
2016-12-26 9:36 ` Chen Feng
2016-12-26 9:36 ` [RESEND 2/2] arm64: dts: Add dts files for Hisilicon " Chen Feng
2016-12-26 9:36 ` Chen Feng
2016-12-26 9:36 ` Chen Feng
2017-01-05 3:28 ` Chen Feng
2017-01-05 3:28 ` Chen Feng
2017-01-05 3:28 ` Chen Feng
2017-01-05 9:40 ` Will Deacon [this message]
2017-01-05 9:40 ` Will Deacon
2017-01-05 9:40 ` Will Deacon
2017-01-05 14:14 ` Andy Gross
2017-01-05 14:14 ` Andy Gross
2017-01-05 14:14 ` Andy Gross
2017-01-06 0:59 ` Chen Feng
2017-01-06 0:59 ` Chen Feng
2017-01-06 0:59 ` Chen Feng
2017-01-03 16:52 ` [RESEND 1/2] document: dt: add binding for " Rob Herring
2017-01-03 16:52 ` Rob Herring
2017-01-03 16:52 ` Rob Herring
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=20170105094045.GA679@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.