From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: "Uwe Kleine-König"
<u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
entwicklung-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org
Subject: Re: [PATCH v2] dtc: Add an option to generate __local_fixups__ and __fixups__
Date: Tue, 23 May 2023 13:09:03 +1000 [thread overview]
Message-ID: <ZGwuT50YlXmtfylW@yekko> (raw)
In-Reply-To: <20230522142032.5e4rqg7iokta5vkp-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
On Mon, May 22, 2023 at 04:20:32PM +0200, Uwe Kleine-König wrote:
> On Mon, May 22, 2023 at 07:06:16PM +1000, David Gibson wrote:
> > On Mon, May 22, 2023 at 10:16:29AM +0200, Uwe Kleine-König wrote:
> > > This happens implicitly for dts files with a /plugin/ tag.
> >
> > Remind me what the use case for this is?
>
> The idea is to have enough information in a dtb file to restore the tags
> and phandle-refs. Look for "[PATCH] dtc: When compiling to dts interpret
> /__symbols__ and /__local_fixups__" in your inbox.
>
> Is this a request to improve the commit log? If so, maybe:
>
> dtc: Add an option to generate __local_fixups__ and __fixups__
>
> This records detailed usage of labels in a dtb that can
> later be used to restore labels when compiling back to dts
> format.
Yes, having that extra context in the commit message would be good,
thanks.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-05-23 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 8:16 [PATCH v2] dtc: Add an option to generate __local_fixups__ and __fixups__ Uwe Kleine-König
[not found] ` <20230522081629.385489-1-u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2023-05-22 9:06 ` David Gibson
2023-05-22 14:20 ` Uwe Kleine-König
[not found] ` <20230522142032.5e4rqg7iokta5vkp-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2023-05-23 3:09 ` David Gibson [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=ZGwuT50YlXmtfylW@yekko \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=entwicklung-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).