From: Christoph Hellwig <hch@infradead.org>
To: Parshuram Thombare <pthombar@cadence.com>
Cc: axboe@kernel.dk, vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, mchehab+samsung@kernel.org,
gregkh@linuxfoundation.org, davem@davemloft.net,
akpm@linux-foundation.org, nicolas.ferre@microchip.com,
arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
adouglas@cadence.com, jank@cadence.com, rafalc@cadence.com
Subject: Re: [PATCH 2/2] scsi: ufs: add inline crypto support to UFS HCD
Date: Tue, 11 Dec 2018 06:07:23 -0800 [thread overview]
Message-ID: <20181211140723.GB6576@infradead.org> (raw)
In-Reply-To: <20181211095027.GA3316@lvlogina.cadence.com>
On Tue, Dec 11, 2018 at 09:50:27AM +0000, Parshuram Thombare wrote:
> Add real time crypto support to UFS HCD using new device
> mapper 'crypto-ufs'. dmsetup tool can be used to enable
> real time / inline crypto support using device mapper
> 'crypt-ufs'.
Can you point to where in the UFS spec this support is specified?
next prev parent reply other threads:[~2018-12-11 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 9:50 [PATCH 2/2] scsi: ufs: add inline crypto support to UFS HCD Parshuram Thombare
2018-12-11 12:03 ` Greg KH
2018-12-12 5:29 ` Parshuram Raju Thombare
2018-12-11 14:07 ` Christoph Hellwig [this message]
2018-12-11 18:16 ` Eric Biggers
2018-12-12 5:51 ` Parshuram Raju Thombare
2018-12-13 19:39 ` Ladvine D Almeida
2018-12-13 19:42 ` Jens Axboe
2018-12-13 20:04 ` Ladvine D Almeida
2018-12-13 20:11 ` Jens Axboe
2018-12-14 5:43 ` Parshuram Raju Thombare
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=20181211140723.GB6576@infradead.org \
--to=hch@infradead.org \
--cc=adouglas@cadence.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jank@cadence.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pthombar@cadence.com \
--cc=rafalc@cadence.com \
--cc=vinholikatti@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).