public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>,
	arm@kernel.org, soc@kernel.org
Cc: Jon Hunter <jonathanh@nvidia.com>,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>
Subject: Re: [GIT PULL 1/4] dt-bindings: Changes for v6.20-rc1
Date: Fri, 23 Jan 2026 08:52:58 +0100	[thread overview]
Message-ID: <3b81369e-8cc7-4e9f-98ca-e6f528e1cab8@kernel.org> (raw)
In-Reply-To: <53d3a98f-3ad8-43c0-9094-39f229a5b698@kernel.org>

On 23/01/2026 08:47, Krzysztof Kozlowski wrote:
> 
>>
>> Jon Hunter (4):
>>       dt-bindings: tegra: pmc: Update aotag as an optional aperture
> 
> ...
> 
>>       ASoC: dt-bindings: realtek,rt5640: Document mclk
>>       ASoC: dt-bindings: realtek,rt5640: Update jack-detect
>>       ASoC: dt-bindings: realtek,rt5640: Document port node
> 
> No, Mark always promptly picks up bindings patches, so I do not
> understand why these are here. These should go via subsystem maintainer.

Heh, and Mark actually did take them on 9th of Jan, so you just
duplicated the patches by taking them one week later. Mark also sends TY
letters so you were notified these are picked up.

Also Rob was fixing the same in separate patchset and Mark also took
these, but then Mark handles the conflicts since its all in his own tree.

These should have never been picked up one week later after Mark to
Tegra soc tree. Please drop.

Best regards,
Krzysztof


  reply	other threads:[~2026-01-23  7:53 UTC|newest]

Thread overview: 13+ 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-22 10:08 ` [GIT PULL 1/4] dt-bindings: " 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 [this message]
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=3b81369e-8cc7-4e9f-98ca-e6f528e1cab8@kernel.org \
    --to=krzk@kernel.org \
    --cc=arm@kernel.org \
    --cc=broonie@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=soc@kernel.org \
    --cc=thierry.reding@gmail.com \
    /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