All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Rob Herring <robh@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] Stable branch for .dts to .dtso rename
Date: Mon, 21 Nov 2022 14:52:23 +0000	[thread overview]
Message-ID: <166904234396.4359.14539414950496081717.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221118211103.GA1334449-robh@kernel.org>

Hello:

This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Fri, 18 Nov 2022 15:11:03 -0600 you 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.
> 
> [...]

Here is the summary with links:
  - [GIT,PULL] Stable branch for .dts to .dtso rename
    https://git.kernel.org/soc/soc/c/cdd1db76607d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-11-21 14:52 UTC|newest]

Thread overview: 7+ 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-18 21:11 ` Rob Herring
2022-11-19  6:35 ` Shawn Guo
2022-11-19  6:35   ` Shawn Guo
2022-11-21  9:43 ` Geert Uytterhoeven
2022-11-21  9:43   ` Geert Uytterhoeven
2022-11-21 14:52 ` patchwork-bot+linux-soc [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=166904234396.4359.14539414950496081717.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=robh@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.