From: Jan Kiszka <jan.kiszka@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: florian.bezdeka@siemens.com, daniel.bovensiepen@siemens.com
Subject: Re: [PATCH 0/3] Extend u-boot-script for DT overlays
Date: Mon, 4 Sep 2023 08:05:42 +0200 [thread overview]
Message-ID: <f50639ed-d12f-47b0-977f-225df395d086@siemens.com> (raw)
In-Reply-To: <20230904055133.1851073-1-felix.moessbauer@siemens.com>
On 04.09.23 07:51, Felix Moessbauer wrote:
> This series re-proposes the reverted u-boot patches 60575d11 and
> a2e734a4, as the corresponding discussions now have been finished.
>
> In addition, p1 adds a comment about the special handling of the
> OVERLAYS u-boot variable. It does not contain any functional
> changes to the original patchset.
>
> The series has been rebased onto next.
>
> Best regards,
> Felix Moessbauer
>
> Felix Moessbauer (3):
> add comment about content of u-boot OVERLAYS var
> u-boot-script: add support to use builtin dt
> use builtin DT for nanopi-neo target
>
> .../lib/wic/canned-wks/nanopi-neo.wks.in | 4 ++--
> .../u-boot-script/files/u-boot-script | 3 +++
> .../u-boot-script/files/update-u-boot-script | 17 +++++++++++++----
> .../lib/wic/plugins/source/rootfs-u-boot.py | 3 +++
> 4 files changed, 21 insertions(+), 6 deletions(-)
>
Looks good to me now. My question on patch 2 shouldn't block things.
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2023-09-04 6:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 5:51 Felix Moessbauer
2023-09-04 5:51 ` [PATCH 1/3] add comment about content of u-boot OVERLAYS var Felix Moessbauer
2023-09-04 5:51 ` [PATCH 2/3] u-boot-script: add support to use builtin dt Felix Moessbauer
2023-09-04 6:05 ` Jan Kiszka
2023-09-04 7:09 ` MOESSBAUER, Felix
2023-09-04 5:51 ` [PATCH 3/3] use builtin DT for nanopi-neo target Felix Moessbauer
2023-09-04 6:05 ` Jan Kiszka [this message]
2023-09-22 4:23 ` [PATCH 0/3] Extend u-boot-script for DT overlays Uladzimir Bely
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=f50639ed-d12f-47b0-977f-225df395d086@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=daniel.bovensiepen@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.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