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 3/6] dt-bindings: Changes for v6.5-rc1
Date: Wed, 14 Jun 2023 11:27:04 +0200 [thread overview]
Message-ID: <ZImH6MwUTGA6s16Q@orome> (raw)
In-Reply-To: <20230609193620.2275240-3-thierry.reding@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
On Fri, Jun 09, 2023 at 09:36:17PM +0200, Thierry Reding wrote:
> Hi ARM SoC maintainers,
>
> The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
>
> Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.5-dt-bindings
>
> for you to fetch changes up to 5f027147e4796e9fc11083b2ad50a91c1ac36ede:
>
> dt-bindings: tegra: Document Jetson Orin Nano Developer Kit (2023-06-06 14:39:20 +0200)
>
> Thanks,
> Thierry
>
> ----------------------------------------------------------------
> dt-bindings: Changes for v6.5-rc1
>
> Several new modules and devices are documented and fixes incorporated
> for the Tegra234 GPIO controller pin mappings as well as the possible
> Tegra XUDC PHY connections.
>
> ----------------------------------------------------------------
> Prathamesh Shete (1):
> dt-bindings: gpio: Remove FSI domain ports on Tegra234
Hi Arnd, Olof,
turns out that this patch in particular is more problematic than
initially thought and is causing issues for various distributions.
I think we want to back out this one patch and replace it by a version
that simply removes the wrong FSI ports without renumbering the
subsequent ones.
The tegra-for-6.5-memory and tegra-for-6.5-arm64-dt tags are based on an
earlier point of the dt-bindings branch, so it should be fine to pull
those in irrespective of this.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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 3/6] dt-bindings: Changes for v6.5-rc1
Date: Wed, 14 Jun 2023 11:27:04 +0200 [thread overview]
Message-ID: <ZImH6MwUTGA6s16Q@orome> (raw)
In-Reply-To: <20230609193620.2275240-3-thierry.reding@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1531 bytes --]
On Fri, Jun 09, 2023 at 09:36:17PM +0200, Thierry Reding wrote:
> Hi ARM SoC maintainers,
>
> The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
>
> Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.5-dt-bindings
>
> for you to fetch changes up to 5f027147e4796e9fc11083b2ad50a91c1ac36ede:
>
> dt-bindings: tegra: Document Jetson Orin Nano Developer Kit (2023-06-06 14:39:20 +0200)
>
> Thanks,
> Thierry
>
> ----------------------------------------------------------------
> dt-bindings: Changes for v6.5-rc1
>
> Several new modules and devices are documented and fixes incorporated
> for the Tegra234 GPIO controller pin mappings as well as the possible
> Tegra XUDC PHY connections.
>
> ----------------------------------------------------------------
> Prathamesh Shete (1):
> dt-bindings: gpio: Remove FSI domain ports on Tegra234
Hi Arnd, Olof,
turns out that this patch in particular is more problematic than
initially thought and is causing issues for various distributions.
I think we want to back out this one patch and replace it by a version
that simply removes the wrong FSI ports without renumbering the
subsequent ones.
The tegra-for-6.5-memory and tegra-for-6.5-arm64-dt tags are based on an
earlier point of the dt-bindings branch, so it should be fine to pull
those in irrespective of 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:[~2023-06-14 9:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 19:36 [GIT PULL 1/6] soc/tegra: Changes for v6.5-rc1 Thierry Reding
2023-06-09 19:36 ` Thierry Reding
2023-06-09 19:36 ` [GIT PULL 2/6] firmware: tegra: " Thierry Reding
2023-06-09 19:36 ` Thierry Reding
2023-06-09 19:36 ` [GIT PULL 3/6] dt-bindings: " Thierry Reding
2023-06-09 19:36 ` Thierry Reding
2023-06-14 9:27 ` Thierry Reding [this message]
2023-06-14 9:27 ` Thierry Reding
2023-06-20 16:26 ` [GIT PULL v2] " Thierry Reding
2023-06-20 16:26 ` Thierry Reding
2023-07-05 20:42 ` patchwork-bot+linux-soc
2023-06-09 19:36 ` [GIT PULL 4/6] memory: tegra: " Thierry Reding
2023-06-09 19:36 ` Thierry Reding
2023-06-09 19:36 ` [GIT PULL 5/6] PCI: " Thierry Reding
2023-06-09 19:36 ` Thierry Reding
2023-06-09 19:36 ` [GIT PULL 6/6] arm64: tegra: Device tree changes " Thierry Reding
2023-06-09 19:36 ` Thierry Reding
2023-06-20 21:21 ` [GIT PULL 1/6] soc/tegra: Changes " patchwork-bot+linux-soc
2023-06-21 20:30 ` patchwork-bot+linux-soc
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=ZImH6MwUTGA6s16Q@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 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.