From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: arm@kernel.org, soc@kernel.org, Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL v2 4/7] dt-bindings: Changes for v6.2-rc1
Date: Tue, 29 Nov 2022 11:16:23 -0600 [thread overview]
Message-ID: <20221129171623.GA3838985-robh@kernel.org> (raw)
In-Reply-To: <20221121171239.2041835-4-thierry.reding@gmail.com>
On Mon, Nov 21, 2022 at 06:12:36PM +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-v2
>
> for you to fetch changes up to 97351cd8bea8e284cf62b4b7f35fa12059b47d7f:
>
> dt-bindings: usb: tegra-xusb: Convert to json-schema (2022-11-21 13:27:30 +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 (1):
> dt-bindings: tegra: Update headers for Tegra234
>
> Mikko Perttunen (2):
> dt-bindings: Add headers for NVDEC on Tegra234
> dt-bindings: Add bindings for Tegra234 NVDEC
>
> Sandipan Patra (1):
> dt-bindings: pwm: tegra: Document Tegra234 PWM
>
> Thierry Reding (4):
> dt-bindings: pinctrl: tegra: Convert to json-schema
> dt-bindings: pinctrl: tegra194: Separate instances
> dt-bindings: pwm: tegra: Convert to json-schema
> dt-bindings: usb: tegra-xusb: Convert to json-schema
This one has warnings due to upstream dtc changes. Details here[1].
Rob
[1] https://lore.kernel.org/all/CAL_JsqKFS5nKRihLL60zfqtNujrYGaxN7sp7SbYA_ajC4w2rpQ@mail.gmail.com/
_______________________________________________
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-29 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 17:12 [GIT PULL v2 1/7] soc/tegra: Changes for v6.2-rc1 Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 2/7] firmware: tegra: " Thierry Reding
2022-11-22 21:25 ` Arnd Bergmann
2022-11-23 11:33 ` Thierry Reding
2022-11-23 13:23 ` Arnd Bergmann
2022-11-25 10:12 ` Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 3/7] clk: " Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 4/7] dt-bindings: " Thierry Reding
2022-11-29 17:16 ` Rob Herring [this message]
2022-11-21 17:12 ` [GIT PULL v2 5/7] memory: tegra: " Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 6/7] ARM: tegra: Device tree changes " Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 7/7] arm64: " Thierry Reding
2022-11-22 22:09 ` Arnd Bergmann
2022-11-23 11:36 ` 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=20221129171623.GA3838985-robh@kernel.org \
--to=robh@kernel.org \
--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 \
--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;
as well as URLs for NNTP newsgroup(s).