From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] dts: arm64: add LS1043A DPAA support
Date: Mon, 27 Mar 2017 16:55:22 +0800 [thread overview]
Message-ID: <20170327085520.GS30608@dragon> (raw)
In-Reply-To: <HE1PR04MB1129DA747FC5B7B977CADF43EC330@HE1PR04MB1129.eurprd04.prod.outlook.com>
On Mon, Mar 27, 2017 at 08:11:33AM +0000, Madalin-Cristian Bucur wrote:
> Complex it is, mirroring the IP, but messy it is a word I would not use.
Well, just my personal opinion.
Shawn
next prev parent reply other threads:[~2017-03-27 8:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 15:35 [PATCH v2 0/2] dts: arm64: add DPAA 1 support for ARM based SoCs Madalin Bucur
2017-03-01 15:35 ` [PATCH v2 1/2] dts: arm64: add LS1043A DPAA support Madalin Bucur
2017-03-14 7:07 ` Shawn Guo
2017-03-22 10:58 ` Madalin-Cristian Bucur
2017-03-27 6:27 ` Shawn Guo
2017-03-27 7:03 ` Madalin-Cristian Bucur
2017-03-27 7:55 ` Shawn Guo
2017-03-27 8:11 ` Madalin-Cristian Bucur
2017-03-27 8:55 ` Shawn Guo [this message]
2017-03-01 15:35 ` [PATCH v2 2/2] dts: arm64: add LS1046A " Madalin Bucur
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=20170327085520.GS30608@dragon \
--to=shawnguo@kernel.org \
--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 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).