public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	U-Boot Custodians <u-boot-custodians@lists.denx.de>,
	Marek Vasut <marex@denx.de>,
	Pavel Herrmann <morpheus.ibis@gmail.com>
Subject: Re: [PATCH v4 10/11] dm: Add support for handling old u-boot, dm- tags
Date: Mon, 13 Feb 2023 08:53:07 +0100	[thread overview]
Message-ID: <97bd9ace-295a-e7e6-68e8-7dd5dad164f2@amd.com> (raw)
In-Reply-To: <Y+klh6H/HirTnUAb@bill-the-cat>



On 2/12/23 18:44, Tom Rini wrote:
> On Fri, Feb 10, 2023 at 08:28:56AM -0700, Simon Glass wrote:
> 
>> Add a CONFIG option to deal with this automatically, printing a warning
>> when U-Boot starts up. This can be useful if the device tree comes from
>> another project.
>>
>> We will maintain this through the 2023.07 release, providing 6 months
>> for people to notice.
>>
>> Signed-off-by: Simon Glass <sjg@chromium.org>
> 
> Adding Michal since he got lost by accident on this iteration. Does that
> sound like enough time to get the tooling you know of updated?
> 

This patch makes sense to me and provide good migration path. Thanks!

In connection to have tree working all the time for bisecting reasons I think 
the whole series should be a little bit rearranged and this shouldn't be the 
patch 10/11 but very early.
But I will let Tom to decide if this should be rearranged or not.

Acked-by: Michal Simek <michal.simek@amd.com>

Thanks,
Michal


  parent reply	other threads:[~2023-02-13  7:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 15:28 [PATCH v4 00/11] dm: Move to new driver model schema for device tree tags Simon Glass
2023-02-10 15:28 ` [PATCH v4 01/11] schemas: Add schema for U-Boot driver model 'phase tags' Simon Glass
2023-02-10 15:28 ` [PATCH v4 02/11] dm: dts: Convert driver model tags to use new schema Simon Glass
2023-02-10 15:28 ` [PATCH v4 03/11] dm: doc: Update device tree binding docs for " Simon Glass
2023-02-10 15:28 ` [PATCH v4 04/11] dm: doc: Update documentation for new driver model schema Simon Glass
2023-02-10 15:28 ` [PATCH v4 05/11] dm: doc: Move to " Simon Glass
2023-02-10 15:28 ` [PATCH v4 06/11] dm: treewide: Complete migration " Simon Glass
2023-02-10 15:28 ` [PATCH v4 07/11] checkpatch: Add a warning for pre-schema driver model tags Simon Glass
2023-02-10 15:28 ` [PATCH v4 08/11] CI: Add a check " Simon Glass
2023-02-10 15:28 ` [PATCH v4 09/11] test: Add a way to set the environment for a pytest Simon Glass
2023-02-10 15:28 ` [PATCH v4 10/11] dm: Add support for handling old u-boot,dm- tags Simon Glass
2023-02-12 17:44   ` [PATCH v4 10/11] dm: Add support for handling old u-boot, dm- tags Tom Rini
2023-02-12 23:15     ` Simon Glass
2023-02-13  1:10       ` Tom Rini
2023-02-13  4:27         ` Simon Glass
2023-02-13  7:53     ` Michal Simek [this message]
2023-02-13 14:45       ` Simon Glass
2023-02-10 15:28 ` [PATCH v4 11/11] dm: test: Add a test for the various migration combinations Simon Glass

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=97bd9ace-295a-e7e6-68e8-7dd5dad164f2@amd.com \
    --to=michal.simek@amd.com \
    --cc=marex@denx.de \
    --cc=morpheus.ibis@gmail.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot-custodians@lists.denx.de \
    --cc=u-boot@lists.denx.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