From: Thierry Reding <thierry.reding@gmail.com>
To: arm@kernel.org, soc@kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/5] arm64: tegra: Default configuration updates for v6.10-rc1
Date: Fri, 26 Apr 2024 20:05:18 +0200 [thread overview]
Message-ID: <20240426180519.3972626-5-thierry.reding@gmail.com> (raw)
In-Reply-To: <20240426180519.3972626-1-thierry.reding@gmail.com>
Hi ARM SoC maintainers,
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-6.10-arm64-defconfig
for you to fetch changes up to 4d4d3fe6b3cc2a0b2a334a08bb9c64ba1dcbbea4:
arm64: defconfig: Enable Tegra Security Engine (2024-04-26 17:31:44 +0200)
Thanks,
Thierry
----------------------------------------------------------------
arm64: tegra: Default configuration updates for v6.10-rc1
Enables the Security Engine driver for the corresponding devices found
on Tegra234.
----------------------------------------------------------------
Akhil R (1):
arm64: defconfig: Enable Tegra Security Engine
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
prev parent reply other threads:[~2024-04-26 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 18:05 [GIT PULL 1/5] soc/tegra: Changes for v6.10-rc1 Thierry Reding
2024-04-26 18:05 ` [GIT PULL 2/5] dt-bindings: " Thierry Reding
2024-04-26 18:05 ` [GIT PULL 3/5] ARM: tegra: " Thierry Reding
2024-04-26 18:05 ` [GIT PULL 4/5] arm64: " Thierry Reding
2024-04-26 18:05 ` Thierry Reding [this message]
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=20240426180519.3972626-5-thierry.reding@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).