public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
	bjorn.andersson@oss.qualcomm.com, arnd@arndb.de
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Manivannan Sadhasivam <mani@kernel.org>
Subject: Re: [RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers
Date: Thu, 30 Oct 2025 20:48:48 +0100	[thread overview]
Message-ID: <27841a96-b8a5-44aa-b0ef-d8bab9ba3477@kernel.org> (raw)
In-Reply-To: <20251030095509.5877-1-manivannan.sadhasivam@oss.qualcomm.com>

On 30/10/2025 10:55, Manivannan Sadhasivam wrote:
> These drivers will allow using the crypto functionalities of the UFS
> device, like Inline Crypto Encryption. Both of these drivers are of type
> 'bool', so they cannot be built as modules.

Is there any device benefiting from these? Which board?

> 
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>

You do not need the second tag. You send it via oss.qualcomm.com which
is still valid.

Best regards,
Krzysztof

  parent reply	other threads:[~2025-10-30 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30  9:55 [RESEND PATCH] arm64: defconfig: Enable SCSI UFS Crypto and Block Inline encryption drivers Manivannan Sadhasivam
2025-10-30 18:46 ` Bjorn Andersson
2025-10-30 19:48 ` Krzysztof Kozlowski [this message]
2025-10-31  6:24   ` Manivannan Sadhasivam
2025-10-31  7:45     ` Krzysztof Kozlowski
2025-10-31  8:15       ` Manivannan Sadhasivam

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=27841a96-b8a5-44aa-b0ef-d8bab9ba3477@kernel.org \
    --to=krzk@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=manivannan.sadhasivam@oss.qualcomm.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