From: Shawn Guo <shawnguo@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: soc@kernel.org, Li Yang <leoyang.li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Davis <afd@ti.com>, Michal Simek <michal.simek@amd.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Frank Rowand <frowand.list@gmail.com>,
Frank Wunderlich <linux@fw-web.de>
Subject: Re: [GIT PULL] Stable branch for .dts to .dtso rename
Date: Sat, 19 Nov 2022 14:35:24 +0800 [thread overview]
Message-ID: <20221119063523.GP16229@T480> (raw)
In-Reply-To: <20221118211103.GA1334449-robh@kernel.org>
On Fri, Nov 18, 2022 at 03:11:03PM -0600, Rob Herring wrote:
> .dts files for overlays are getting renamed to .dtso. The kbuild support
> for that in in this stable branch. The .dts patches that depend on this
> are here[1]. There's also some new .dts overlay files posted[2].
>
> I'll leave it to the SoC and sub-arch maintainers to decide how you all
> want to handle it from here. Either SoC maintainers can take this branch
> and dependent rename patches or each sub-arch can. In any case, I would
> like it converted over in 6.2 so we can remove .dts -> .dtbo build
> support ASAP and not be carrying both.
>
> Rob
>
> [1] https://lore.kernel.org/all/20221024173434.32518-1-afd@ti.com/
Thanks, Rob! I pulled your branch and applied "freescale" one.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-19 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 21:11 [GIT PULL] Stable branch for .dts to .dtso rename Rob Herring
2022-11-19 6:35 ` Shawn Guo [this message]
2022-11-21 9:43 ` Geert Uytterhoeven
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=20221119063523.GP16229@T480 \
--to=shawnguo@kernel.org \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.com \
--cc=michal.simek@amd.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=soc@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