public inbox for soc@kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1
Date: Tue, 27 Jan 2026 11:21:46 +0100	[thread overview]
Message-ID: <aXiOqLYwBxrvErjP@orome> (raw)
In-Reply-To: <176901122359.951664.14976320641854335179.git-patchwork-notify@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 3885 bytes --]

On Wed, Jan 21, 2026 at 04:00:23PM +0000, patchwork-bot+linux-soc@kernel.org wrote:
> Hello:
> 
> This pull request was applied to soc/soc.git (for-next)
> by Arnd Bergmann <arnd@arndb.de>:
> 
> On Sun, 18 Jan 2026 09:03:00 +0100 you wrote:
> > Hi ARM SoC maintainers,
> > 
> > The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
> > 
> >   Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
> > 
> > are available in the Git repository at:
> > 
> > [...]
> 
> Here is the summary with links:
>   - [GIT,PULL,1/4] dt-bindings: Changes for v6.20-rc1
>     (no matching commit)

Hi Arnd,

is it too late to back out this particular pull request? I missed that
Mark had already pulled some of the patches in this branch to the ASoC
tree, so now we have two version of this (well, actually three because
Rob had a set of changes that were also cleaning up some warning that
these patches were) and everyones getting really annoyed.

I think you mentioned at some point that you can't easily undo these
merged, in which case that's fine too and I'll take the full blame for
this. But if it's possible, below is an updated pull request.

Thanks,
Thierry

--- >8 ---

The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:

  Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.20-dt-bindings-v2

for you to fetch changes up to d262d030baef287da33344a932639aab5f913c3a:

  dt-bindings: display: tegra: document Tegra30 VI and VIP (2026-01-17 01:31:19 +0100)

----------------------------------------------------------------
dt-bindings: Changes for v6.20-rc1

This series updates various DT bindings for Tegra architecture,
primarily focusing on schema validation fixes and new feature
documentation for Tegra234 and Tegra264 SoCs. Key changes include
converting Tegra20 NAND bindings to YAML, and updating memory, DMA, and
IOMMU definitions for Tegra264 (introducing CMDQV and DBB clock
support). Additionally, it resolves legacy warnings for Tegra30/132
display and VI interfaces.

----------------------------------------------------------------
Ashish Mhetre (1):
      dt-bindings: iommu: Add NVIDIA Tegra CMDQV support

Charan Pedumuru (1):
      dt-bindings: mtd: nvidia,tegra20-nand: convert to DT schema

Jon Hunter (1):
      dt-bindings: tegra: pmc: Update aotag as an optional aperture

Svyatoslav Ryhel (2):
      dt-bindings: display: tegra: document Tegra132 MIPI calibration device
      dt-bindings: display: tegra: document Tegra30 VI and VIP

Thierry Reding (1):
      dt-bindings: memory: tegra: Document DBB clock for Tegra264

sheetal (1):
      dt-bindings: dma: Update ADMA bindings for tegra264

 .../bindings/arm/tegra/nvidia,tegra186-pmc.yaml    |  11 ++-
 .../display/tegra/nvidia,tegra114-mipi.yaml        |   1 +
 .../bindings/display/tegra/nvidia,tegra20-vi.yaml  |  19 ++--
 .../bindings/display/tegra/nvidia,tegra20-vip.yaml |   9 +-
 .../bindings/dma/nvidia,tegra210-adma.yaml         |  15 ++-
 .../devicetree/bindings/iommu/arm,smmu-v3.yaml     |  27 +++++-
 .../bindings/iommu/nvidia,tegra264-cmdqv.yaml      |  42 +++++++++
 .../memory-controllers/nvidia,tegra186-mc.yaml     |  13 +++
 .../bindings/mtd/nvidia,tegra20-nand.yaml          | 102 +++++++++++++++++++++
 .../bindings/mtd/nvidia-tegra20-nand.txt           |  64 -------------
 MAINTAINERS                                        |   2 +-
 11 files changed, 225 insertions(+), 80 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/iommu/nvidia,tegra264-cmdqv.yaml
 create mode 100644 Documentation/devicetree/bindings/mtd/nvidia,tegra20-nand.yaml
 delete mode 100644 Documentation/devicetree/bindings/mtd/nvidia-tegra20-nand.txt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-01-27 10:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18  8:03 [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1 Thierry Reding
2026-01-18  8:03 ` [GIT PULL 2/4] soc/tegra: " Thierry Reding
2026-01-18  8:03 ` [GIT PULL 3/4] ARM: tegra: Device tree changes " Thierry Reding
2026-01-18  8:03 ` [GIT PULL 4/4] arm64: tegra: Changes " Thierry Reding
2026-01-21 16:00 ` [GIT PULL 1/4] dt-bindings: " patchwork-bot+linux-soc
2026-01-27 10:21   ` Thierry Reding [this message]
2026-01-22 10:08 ` Krzysztof Kozlowski
2026-01-22 11:02   ` Geert Uytterhoeven
2026-01-22 12:20     ` Thierry Reding
2026-01-23  7:43       ` Krzysztof Kozlowski
2026-01-27  9:51         ` Thierry Reding
2026-01-23  7:47 ` Krzysztof Kozlowski
2026-01-23  7:52   ` Krzysztof Kozlowski
2026-01-27 10:05     ` Thierry Reding
2026-01-27 10:02   ` Thierry Reding

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=aXiOqLYwBxrvErjP@orome \
    --to=thierry.reding@gmail.com \
    --cc=arnd@arndb.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