From: Tao Ren <rentao.bupt@gmail.com>
To: Joel Stanley <joel@jms.id.au>
Cc: Tao Ren <taoren@fb.com>, Mark Rutland <mark.rutland@arm.com>,
devicetree <devicetree@vger.kernel.org>,
linux-aspeed <linux-aspeed@lists.ozlabs.org>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/4] ARM: dts: aspeed: add dtsi for Facebook AST2500 Network BMCs
Date: Fri, 1 Nov 2019 10:40:45 -0700 [thread overview]
Message-ID: <20191101174044.GA13557@taoren-ubuntu-R90MNF91> (raw)
In-Reply-To: <CACPK8XcNxs5T=ZC_mRnvkOF_kqS1AvP=9PvMB6w9Fgn_XbtZQw@mail.gmail.com>
On Fri, Nov 01, 2019 at 10:08:35AM +0000, Joel Stanley wrote:
> Hi Tao,
>
> On Mon, 21 Oct 2019 at 19:49, Tao Ren <taoren@fb.com> wrote:
> >
> > The patch series adds "facebook-netbmc-ast2500-common.dtsi" which defines
> > devices that are common cross all Facebook AST2500 Network BMC platforms.
> > The major purpose is to minimize duplicated device entries among Facebook
> > Network BMC dts files.
> >
> > Patch #1 (of 4) adds "facebook-netbmc-ast2500-common.dtsi" file, and the
> > remaining 3 patches update CMM, Minipack and Yamp device tree to consume
> > the new dtsi file.
>
> The patches look okay to me. I modified the file name to match the
> convention used by other device trees in the arm directory, where it
> includes the SOC name first.
>
> I also reworded the commit messages a little.
>
> They have been merged into the aspeed tree for submission to 5.5.
>
> Thanks!
>
> Joel
Got it. Thanks a lot for doing this, Joel.
Cheers,
Tao
> >
> > Tao Ren (4):
> > ARM: dts: aspeed: add dtsi for Facebook AST2500 Network BMCs
> > ARM: dts: aspeed: cmm: include dtsi for common network BMC devices
> > ARM: dts: aspeed: minipack: include dtsi for common network BMC
> > devices
> > ARM: dts: aspeed: yamp: include dtsi for common network BMC devices
> >
> > arch/arm/boot/dts/aspeed-bmc-facebook-cmm.dts | 66 ++++---------
> > .../boot/dts/aspeed-bmc-facebook-minipack.dts | 59 ++++--------
> > .../arm/boot/dts/aspeed-bmc-facebook-yamp.dts | 62 +-----------
> > .../dts/facebook-netbmc-ast2500-common.dtsi | 96 +++++++++++++++++++
> > 4 files changed, 136 insertions(+), 147 deletions(-)
> > create mode 100644 arch/arm/boot/dts/facebook-netbmc-ast2500-common.dtsi
> >
> > --
> > 2.17.1
> >
prev parent reply other threads:[~2019-11-01 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 19:48 [PATCH 0/4] ARM: dts: aspeed: add dtsi for Facebook AST2500 Network BMCs Tao Ren
2019-10-21 19:48 ` [PATCH 1/4] " Tao Ren
2019-11-01 10:12 ` Joel Stanley
2019-11-01 17:42 ` Tao Ren
2019-10-21 19:48 ` [PATCH 2/4] ARM: dts: aspeed: cmm: include dtsi for common network BMC devices Tao Ren
2019-10-21 19:48 ` [PATCH 3/4] ARM: dts: aspeed: minipack: " Tao Ren
2019-10-21 19:48 ` [PATCH 4/4] ARM: dts: aspeed: yamp: " Tao Ren
2019-11-01 10:08 ` [PATCH 0/4] ARM: dts: aspeed: add dtsi for Facebook AST2500 Network BMCs Joel Stanley
2019-11-01 17:40 ` Tao Ren [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=20191101174044.GA13557@taoren-ubuntu-R90MNF91 \
--to=rentao.bupt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=taoren@fb.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