Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Emil Renner Berthing <kernel@esmil.dk>,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
	Rob Herring <robh+dt@kernel.org>,
	Daniel Bovensiepen <daniel.bovensiepen@siemens.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/1] riscv: dts: Enable device-tree overlay support for starfive devices
Date: Wed, 12 Jul 2023 17:40:27 +0100	[thread overview]
Message-ID: <20230712-legume-establish-d389b8e40984@spud> (raw)
In-Reply-To: <20230627080620.329873-1-felix.moessbauer@siemens.com>

From: Conor Dooley <conor.dooley@microchip.com>

On Tue, 27 Jun 2023 16:06:20 +0800, Felix Moessbauer wrote:
> Add the '-@' DTC option for the starfive devices. This option
> populates the '__symbols__' node that contains all the necessary symbols
> for supporting device-tree overlays (for instance from the firmware or
> the bootloader) on these devices.
> 
> The starfive devices allow various modules to be connected and this
> enables users to create out-of-tree device-tree overlays for these modules.
> 
> [...]

Applied to riscv-dt-for-next, thanks!

[1/1] riscv: dts: Enable device-tree overlay support for starfive devices
      https://git.kernel.org/conor/c/ef6012f301f7

Thanks,
Conor.

      parent reply	other threads:[~2023-07-12 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  8:06 [PATCH 1/1] riscv: dts: Enable device-tree overlay support for starfive devices Felix Moessbauer
2023-07-06 17:27 ` Palmer Dabbelt
2023-07-10 18:28 ` Conor Dooley
2023-07-12 16:17   ` Emil Renner Berthing
2023-07-12 16:23     ` Conor Dooley
2023-07-12 18:52       ` Emil Renner Berthing
2023-07-20  6:34       ` Walker Chen
2023-07-12 16:40 ` Conor Dooley [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=20230712-legume-establish-d389b8e40984@spud \
    --to=conor@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=daniel.bovensiepen@siemens.com \
    --cc=devicetree@vger.kernel.org \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kernel@esmil.dk \
    --cc=linux-riscv@lists.infradead.org \
    --cc=robh+dt@kernel.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