From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v2 0/4] arm: dts: Aspeed SoC device-tree update
Date: Mon, 18 Jun 2018 14:58:58 +1000 [thread overview]
Message-ID: <20180618045902.11453-1-benh@kernel.crashing.org> (raw)
This series fixes a few things in some Aspeed BMC device trees:
- Fix an error in a memory reserve address on Romulus systems
- Update AST2400 and AST2500 device-trees to add a label to the
SRAM node and add the coprocessor interrupts controller node
along with a binding.
next reply other threads:[~2018-06-18 4:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 4:58 Benjamin Herrenschmidt [this message]
2018-06-18 4:58 ` [PATCH v2 1/4] arm: dts: Fix error in Aspeed OpenPower Romulus device-tree Benjamin Herrenschmidt
2018-06-18 5:16 ` Benjamin Herrenschmidt
2018-06-18 4:59 ` [PATCH v2 2/4] dt-bindings: misc: Aspeed coprocessor interrupt controller Benjamin Herrenschmidt
2018-06-19 6:56 ` Joel Stanley
2018-06-19 6:58 ` Benjamin Herrenschmidt
2018-06-20 19:49 ` Rob Herring
2018-06-20 23:05 ` Benjamin Herrenschmidt
2018-06-18 4:59 ` [PATCH v2 3/4] arm: dts: Update AST2500 device-tree Benjamin Herrenschmidt
2018-06-18 4:59 ` [PATCH v2 4/4] arm: dts: Update AST2400 device-tree Benjamin Herrenschmidt
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=20180618045902.11453-1-benh@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linux-aspeed@lists.ozlabs.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).