From: "Arnd Bergmann" <arnd@arndb.de>
To: kamlesh <kamlesh@ti.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Bjorn Andersson" <quic_bjorande@quicinc.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Thierry Reding" <treding@nvidia.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Mark Brown" <broonie@kernel.org>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Andrew Davis" <afd@ti.com>,
j-choudhary@ti.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Praneeth Bajjuri" <praneeth@ti.com>
Subject: Re: [PATCH] arm64: defconfig: Enable security accelerator driver for TI K3 SoCs
Date: Mon, 17 Apr 2023 16:36:28 +0200 [thread overview]
Message-ID: <081b9317-214d-4879-bbb1-3e5d032a793f@app.fastmail.com> (raw)
In-Reply-To: <20230417132717.1990023-2-kamlesh@ti.com>
On Mon, Apr 17, 2023, at 15:27, kamlesh@ti.com wrote:
> From: Kamlesh Gurudasani <kamlesh@ti.com>
>
> Enable TI's SA2UL driver to support security acceleration on TI K3 SoCs.
>
> Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
> ---
The normal way that platform specific defconfig changes get merged is
through the platform maintainer tree, so in this case the k3 maintainers
would forward the patch to me.
Since it's simple enough, and I've already merged the other k3 patches
for v6.4, I've added this one directly to the soc/defconfig branch.
ARnd
next prev parent reply other threads:[~2023-04-17 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 13:27 [PATCH] arm64: defconfig: Enable crypto test module kamlesh
2023-04-17 13:27 ` [PATCH] arm64: defconfig: Enable security accelerator driver for TI K3 SoCs kamlesh
2023-04-17 14:36 ` Arnd Bergmann [this message]
2023-04-17 14:33 ` [PATCH] arm64: defconfig: Enable crypto test module Arnd Bergmann
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=081b9317-214d-4879-bbb1-3e5d032a793f@app.fastmail.com \
--to=arnd@arndb.de \
--cc=afd@ti.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=j-choudhary@ti.com \
--cc=kamlesh@ti.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=praneeth@ti.com \
--cc=quic_bjorande@quicinc.com \
--cc=rafal@milecki.pl \
--cc=treding@nvidia.com \
--cc=vigneshr@ti.com \
--cc=will@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
all inboxes | Powered by JetHome®