From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] arm: dts: aspeed: Add coprocessor interrupt controller
Date: Tue, 24 Jul 2018 14:36:14 +1000 [thread overview]
Message-ID: <c76640c2d99e9c8b1e3dab664de8ad36d0eb0da3.camel@kernel.crashing.org> (raw)
In-Reply-To: <CACPK8Xe53YJ6GmEk6gyN5DNgEHn5V+CGNSKNE-MNw8Osugf2=Q@mail.gmail.com>
On Tue, 2018-07-24 at 13:59 +0930, Joel Stanley wrote:
> On 24 July 2018 at 13:54, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> > Add the missing node for the CVIC (the coprocessor interrupt
> > controller) and add a label to the SRAM node so it can be
> > referenced from the board device-tree file.
> >
> > OpenBMC-Staging-Count: 1
>
> We shouldn't be putting this in upstream patches.
Ah oops, I accidentally cherry-picked it back out of your tree.
> I can drop it when I apply if there is no other review.
next prev parent reply other threads:[~2018-07-24 4:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 4:24 [PATCH 0/5] arm: dts: aspeed DTS updates for OpenPower Benjamin Herrenschmidt
2018-07-24 4:24 ` [PATCH 1/5] arm: dts: aspeed: Add coprocessor interrupt controller Benjamin Herrenschmidt
2018-07-24 4:29 ` Joel Stanley
2018-07-24 4:36 ` Benjamin Herrenschmidt [this message]
2018-07-24 4:24 ` [PATCH 2/5] arm: dts: OpenPower Romulus system can use coprocessor for FSI Benjamin Herrenschmidt
2018-07-24 4:24 ` [PATCH 3/5] arm: dts: OpenPower Palmetto " Benjamin Herrenschmidt
2018-08-24 0:43 ` Rob Herring
2018-07-24 4:24 ` [PATCH 4/5] arm: dts: Add power8 CFAM dtsi and use it on palmetto Benjamin Herrenschmidt
2018-07-24 4:24 ` [PATCH 5/5] arm: dts: aspeed: Add power9 CFAM dtsi and use it on OpenPower P9 machines Benjamin Herrenschmidt
2018-07-26 19:50 ` Olof Johansson
2018-07-26 23:55 ` 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=c76640c2d99e9c8b1e3dab664de8ad36d0eb0da3.camel@kernel.crashing.org \
--to=benh@kernel.crashing.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).