From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] ARM: dts: renesas: Add Inter Connect RAM
Date: Mon, 10 Jul 2017 11:26:55 +0200 [thread overview]
Message-ID: <20170710092654.GP13680@verge.net.au> (raw)
In-Reply-To: <CAMuHMdU7KC4X8+kOFUBiBw2ZHs=aukf+_1iR+Gjw2M+RgJ6mBQ@mail.gmail.com>
On Mon, Jul 10, 2017 at 10:45:23AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Mon, Jul 10, 2017 at 10:40 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Tue, Jul 04, 2017 at 05:23:11PM +0200, Geert Uytterhoeven wrote:
> >> R-Car Gen2 and RZ/G1 SoCs contain two or three blocks of SRAM, which can be
> >> used for several purposes. One such purpose is holding a jump stub for CPU
> >> core bringup.
> >>
> >> This patch series adds the SRAM blocks to the various DTS files, following
> >> the generic DT bindings for "mmio-sram" in
> >> Documentation/devicetree/bindings/sram/sram.txt. Reserving SRAM for jump
> >> stub for CPU core bringup will be handled in a follow-up series.
> >>
> >> Thanks!
> >
> > Geert, these seem nice and clean to me.
> > Are they ready to be applied?
>
> I think they are.
Thanks, all patches applied for v4.14.
prev parent reply other threads:[~2017-07-10 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 15:23 [PATCH 0/7] ARM: dts: renesas: Add Inter Connect RAM Geert Uytterhoeven
2017-07-04 15:23 ` [PATCH 1/7] ARM: dts: r8a7743: " Geert Uytterhoeven
2017-07-04 15:23 ` [PATCH 2/7] ARM: dts: r8a7745: " Geert Uytterhoeven
2017-07-04 15:23 ` [PATCH 3/7] ARM: dts: r8a7790: " Geert Uytterhoeven
2017-07-04 15:23 ` [PATCH 4/7] ARM: dts: r8a7791: " Geert Uytterhoeven
2017-07-04 15:23 ` [PATCH 5/7] ARM: dts: r8a7792: " Geert Uytterhoeven
2017-07-04 15:23 ` [PATCH 6/7] ARM: dts: r8a7793: " Geert Uytterhoeven
2017-07-04 15:23 ` [PATCH 7/7] ARM: dts: r8a7794: " Geert Uytterhoeven
2017-07-10 8:40 ` [PATCH 0/7] ARM: dts: renesas: " Simon Horman
2017-07-10 8:45 ` Geert Uytterhoeven
2017-07-10 9:26 ` Simon Horman [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=20170710092654.GP13680@verge.net.au \
--to=horms@verge.net.au \
--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