From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Felix Moessbauer <felix.moessbauer@siemens.com>,
Uladzimir Bely <ubely@ilbers.de>
Subject: Re: [PATCH 0/4] Rework and extend u-boot-script for DT overlays
Date: Wed, 9 Aug 2023 09:43:21 +0200 [thread overview]
Message-ID: <ZNNDmag9CNE5E7lk@ilbers.de> (raw)
In-Reply-To: <b981c53cff83d970577981c6b366df3f7be51aaa.camel@ilbers.de>
On 2023-08-09 08:40, Uladzimir Bely wrote:
> On Tue, 2023-08-08 at 12:24 +0200, Jan Kiszka wrote:
> > Revert 2-4, please, there are many open issues.
>
> Would it be OK just to move "origin/next" three commits down (e.g.,
> force push), or these should be separate revert patch(es)?
No need to force-push, we will revert but we'd like to have the discussion on
the list why some patches should be applied separately or what the open issues
are.
With kind regards,
Baurzhan
prev parent reply other threads:[~2023-08-09 7:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 9:37 Felix Moessbauer
2023-08-01 9:37 ` [PATCH 1/4] fix(u-boot-script): use correct ramdisk size Felix Moessbauer
2023-08-03 10:22 ` Gylstorff Quirin
2023-08-01 9:37 ` [PATCH 2/4] refactor loading of DT overlays in uboot Felix Moessbauer
2023-08-08 8:48 ` Jan Kiszka
2023-08-31 4:56 ` MOESSBAUER, Felix
2023-08-01 9:37 ` [PATCH 3/4] u-boot-script: add support to use builtin dt Felix Moessbauer
2023-08-01 9:37 ` [PATCH 4/4] use builtin DT for nanopi-neo target Felix Moessbauer
2023-08-08 8:48 ` Jan Kiszka
2023-08-31 5:34 ` MOESSBAUER, Felix
2023-08-31 7:01 ` Jan Kiszka
2023-08-31 7:07 ` MOESSBAUER, Felix
2023-08-08 7:05 ` [PATCH 0/4] Rework and extend u-boot-script for DT overlays Uladzimir Bely
2023-08-08 10:24 ` Jan Kiszka
2023-08-09 5:40 ` Uladzimir Bely
2023-08-09 7:43 ` Baurzhan Ismagulov [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=ZNNDmag9CNE5E7lk@ilbers.de \
--to=ibr@radix50.net \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=ubely@ilbers.de \
/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