From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org, soc@kernel.org
Cc: Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 4/8] dt-bindings: Changes for v6.2-rc1
Date: Mon, 21 Nov 2022 13:10:01 +0100 [thread overview]
Message-ID: <Y3tqmX4FV4OzOIOz@orome> (raw)
In-Reply-To: <20221119012025.3968358-4-thierry.reding@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1358 bytes --]
On Sat, Nov 19, 2022 at 02:20:21AM +0100, Thierry Reding wrote:
> Hi ARM SoC maintainers,
>
> The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
>
> Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.2-dt-bindings
>
> for you to fetch changes up to 9c812445df0507aa30ddb511a777fc5dd981eb66:
>
> dt-bindings: usb: tegra-xusb: Convert to json-schema (2022-11-18 23:58:45 +0100)
>
> Thanks,
> Thierry
>
> ----------------------------------------------------------------
> dt-bindings: Changes for v6.2-rc1
>
> New memory client IDs and IOMMU stream IDs, as well as new compatible
> strings are introduced to support more hardware on Tegra234. Some device
> tree bindings are converted to json-schema to allow formal validation.
>
> ----------------------------------------------------------------
> Jon Hunter (2):
> dt-bindings: tegra: Update headers for Tegra234
> dt-bindings: memory: Fix typos and definitions for Tegra
I was just testing a new script and noticed that the Fixes: reference in
this patch to the first one no longer matches, so I'll have to respin
this (along with for-6.2/memory and for-6.2/arm64/dt which depend on
this).
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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-21 12:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 1:20 [GIT PULL 1/8] soc/tegra: Changes for v6.2-rc1 Thierry Reding
2022-11-19 1:20 ` [GIT PULL 2/8] firmware: tegra: " Thierry Reding
2022-11-19 1:20 ` [GIT PULL 3/8] clk: " Thierry Reding
2022-11-19 1:20 ` [GIT PULL 4/8] dt-bindings: " Thierry Reding
2022-11-21 12:10 ` Thierry Reding [this message]
2022-11-19 1:20 ` [GIT PULL 5/8] memory: tegra: " Thierry Reding
2022-11-19 1:20 ` [GIT PULL 6/8] ARM: tegra: Device tree changes " Thierry Reding
2022-11-19 1:20 ` [GIT PULL 7/8] arm64: " Thierry Reding
2022-11-19 1:20 ` [GIT PULL 8/8] arm64: tegra: Default configuration updates " 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=Y3tqmX4FV4OzOIOz@orome \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox