From: Kevin Hilman <khilman@baylibre.com>
To: ryder.lee@kernel.org, Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Weijie Gao <weijie.gao@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Ryder Lee <ryder.lee@mediatek.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Steven Liu <steven.liu@mediatek.com>
Subject: Re: [PATCH v1] arm: dts: mediatek: add basic support for MT7629 SoC
Date: Fri, 28 Jun 2019 16:32:18 -0700 [thread overview]
Message-ID: <7hy31lp9q5.fsf@baylibre.com> (raw)
In-Reply-To: <a8ca0018ac8a4c5f61a7a1efc9dc5dccd768628b.1552449524.git.ryder.lee@mediatek.com>
<ryder.lee@kernel.org> writes:
> From: Ryder Lee <ryder.lee@mediatek.com>
>
> This adds basic support for MT7629 reference board.
>
> Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
Just noticing this is not upstream yet.
I did a basic boot test to ramdisk on the mt7629-rfb board donated for
kernelCI (thanks MediaTek!) and it boots just fine.
Tested-by: Kevin Hilman <khilman@baylibre.com>
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: ryder.lee@kernel.org, Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, Ryder Lee <ryder.lee@mediatek.com>,
Steven Liu <steven.liu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Weijie Gao <weijie.gao@mediatek.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] arm: dts: mediatek: add basic support for MT7629 SoC
Date: Fri, 28 Jun 2019 16:32:18 -0700 [thread overview]
Message-ID: <7hy31lp9q5.fsf@baylibre.com> (raw)
In-Reply-To: <a8ca0018ac8a4c5f61a7a1efc9dc5dccd768628b.1552449524.git.ryder.lee@mediatek.com>
<ryder.lee@kernel.org> writes:
> From: Ryder Lee <ryder.lee@mediatek.com>
>
> This adds basic support for MT7629 reference board.
>
> Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
Just noticing this is not upstream yet.
I did a basic boot test to ramdisk on the mt7629-rfb board donated for
kernelCI (thanks MediaTek!) and it boots just fine.
Tested-by: Kevin Hilman <khilman@baylibre.com>
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-28 23:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 8:42 [PATCH v1] arm: dts: mediatek: add basic support for MT7629 SoC ryder.lee
2019-03-13 8:42 ` ryder.lee
2019-03-13 8:42 ` ryder.lee
2019-03-13 12:04 ` Matthias Brugger
2019-03-13 12:04 ` Matthias Brugger
2019-03-13 12:26 ` Matthias Brugger
2019-03-13 12:26 ` Matthias Brugger
2019-03-28 15:06 ` Rob Herring
2019-03-28 15:06 ` Rob Herring
2019-06-28 23:32 ` Kevin Hilman [this message]
2019-06-28 23:32 ` Kevin Hilman
2019-06-29 15:58 ` Ryder Lee
2019-06-29 15:58 ` Ryder Lee
2019-06-29 15:58 ` Ryder Lee
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=7hy31lp9q5.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=steven.liu@mediatek.com \
--cc=weijie.gao@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 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.