From: Christoph Hellwig <hch@infradead.org>
To: Ladvine D Almeida <Ladvine.DAlmeida@synopsys.com>
Cc: "Jens Axboe <axboe@kernel.dk>; Hannes Reinecke <hare@suse.com>;
Johannes Thumshirn <jthumshirn@suse.de>; Omar Sandoval
<osandov@fb.com>; Mike Snitzer <snitzer@redhat.com>; Shaohua Li
<shli@fb.com>; Bart Van Assche <bart.vanassche@wdc.com> ; Keith
Busch <keith.busch@intel.com>; Ming Lei" <ming.lei@redhat.com>,
linux-block@vger.kernel.org,
"linux-kernel@vger.kernel.org; Manjunath M Bettegowda
<manjumb@synopsys.com>; Prabu Thangamuthu <prabut@synopsys.com>;
Tejas Joglekar <joglekar@synopsys.com>; Joao Pinto"
<Joao.Pinto@synopsys.com>
Subject: Re: [PATCH] block: Add block level changes for inline encryption
Date: Fri, 1 Jun 2018 01:13:30 -0700 [thread overview]
Message-ID: <20180601081330.GA13067@infradead.org> (raw)
In-Reply-To: <d3624fab-e6fc-f14d-c780-db703c809068@synopsys.com>
On Mon, May 28, 2018 at 02:43:09PM +0100, Ladvine D Almeida wrote:
>
> This patch introduces new variable under bio structure to
> facilitate inline encryption. This variable is used to
> associate I/O requests to crypto information.
This seems to be missing a whole lot of context. Where is the whole
series showing what you are trying to do?
next prev parent reply other threads:[~2018-06-01 8:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 13:43 [PATCH] block: Add block level changes for inline encryption Ladvine D Almeida
2018-05-28 15:54 ` Jens Axboe
2018-05-31 7:47 ` Ladvine D Almeida
2018-05-31 7:47 ` Ladvine D Almeida
2018-05-31 15:46 ` Jens Axboe
2018-06-01 6:27 ` Ladvine D Almeida
2018-06-01 6:27 ` Ladvine D Almeida
2018-06-01 17:30 ` Jens Axboe
2018-06-01 8:13 ` Christoph Hellwig [this message]
2018-06-06 7:35 ` Ladvine D Almeida
2018-06-07 1:52 ` Jens Axboe
2018-06-07 6:55 ` Ladvine D Almeida
2018-06-07 6:55 ` Ladvine D Almeida
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=20180601081330.GA13067@infradead.org \
--to=hch@infradead.org \
--cc=Joao.Pinto@synopsys.com \
--cc=Ladvine.DAlmeida@synopsys.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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 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.