From: woogyom.kim@gmail.com (Milo Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH resend v4 2/3] ARM: dts: imx6: Support Savageboard dual
Date: Tue, 10 Jan 2017 13:31:38 +0900 [thread overview]
Message-ID: <02b61197-c906-c072-1ee9-d6324a55f01d@gmail.com> (raw)
In-Reply-To: <20170110032736.GX20956@dragon>
On 01/10/2017 12:27 PM, Shawn Guo wrote:
> On Wed, Jan 04, 2017 at 04:04:36PM +0900, Milo Kim wrote:
>> Common savageboard DT file is used for board support.
>> Add the vendor name and specify the dtb file for i.MX6Q build.
>>
>> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
>> Signed-off-by: Milo Kim <woogyom.kim@gmail.com>
>> ---
>> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> The bindings change should be ideally a separate patch. But since Rob
> seems to be fine with it this time, I just applied the whole series.
Got it. Thanks for taking this.
Best regards,
Milo
prev parent reply other threads:[~2017-01-10 4:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 7:04 [PATCH resend v4 2/3] ARM: dts: imx6: Support Savageboard dual Milo Kim
2017-01-04 14:38 ` Rob Herring
2017-01-10 3:27 ` Shawn Guo
2017-01-10 4:31 ` Milo Kim [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=02b61197-c906-c072-1ee9-d6324a55f01d@gmail.com \
--to=woogyom.kim@gmail.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 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).