mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Ladvine D Almeida <Ladvine.DAlmeida@synopsys.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: Hannes Reinecke <hare@suse.com>,
	"ming.lei@redhat.com" <ming.lei@redhat.com>,
	"linux-block@vger.kernel.org" <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>,
	Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH] block: Add block level changes for inline encryption
Date: Wed, 6 Jun 2018 19:52:51 -0600	[thread overview]
Message-ID: <918609fa-8721-0ee1-801e-4c29b64ac9ae@kernel.dk> (raw)
In-Reply-To: <BD7FB879CC136E419544C8E2AE7B9C3020C566@IN01WEMBXA.internal.synopsys.com>

On 6/6/18 1:35 AM, Ladvine D Almeida wrote:
> On Friday 01 June 2018 09:13 AM, Christoph Hellwig wrote:
>> 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?
>>
> Christoph,
> 
> The patches are generated in the below > manner, with a thought of
> sending separately to the MAINTAINERS responsible for each.

What both Christoph and I have said is that it's _impossible_ to review
changes when you don't know what is being built on top of it. The block
change, by itself, is utterly useless. The use case needs to be seen.
But apart from that, my comments on why it's doing it completely
backwards still apply, and I've outlined how you need to fix it. The
patch, in its current form, isn't going anywhere.

-- 
Jens Axboe

  parent reply	other threads:[~2018-06-07  1:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d3624fab-e6fc-f14d-c780-db703c809068@synopsys.com>
     [not found] ` <77544032-b6ff-bc5e-9fec-666e66b2cc70@kernel.dk>
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 17:30         ` Jens Axboe
     [not found] ` <20180601081330.GA13067@infradead.org>
     [not found]   ` <BD7FB879CC136E419544C8E2AE7B9C3020C566@IN01WEMBXA.internal.synopsys.com>
2018-06-07  1:52     ` Jens Axboe [this message]
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=918609fa-8721-0ee1-801e-4c29b64ac9ae@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Joao.Pinto@synopsys.com \
    --cc=Ladvine.DAlmeida@synopsys.com \
    --cc=hare@suse.com \
    --cc=hch@infradead.org \
    --cc=joglekar@synopsys.com \
    --cc=jthumshirn@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manjumb@synopsys.com \
    --cc=ming.lei@redhat.com \
    --cc=prabut@synopsys.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

all inboxes | Powered by JetHome®