From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH for-5.14] cryptoloop: add a deprecation warning
Date: Fri, 27 Aug 2021 10:57:35 -0600 [thread overview]
Message-ID: <e67cdaa4-7d79-7cfd-e377-d15cd62527f0@kernel.dk> (raw)
In-Reply-To: <20210827165528.GA27254@lst.de>
On 8/27/21 10:55 AM, Christoph Hellwig wrote:
> On Fri, Aug 27, 2021 at 10:52:52AM -0600, Jens Axboe wrote:
>> As I said, I don't really care that much about it, but it would be nice
>> to have some actual justification for WHY it should go out asap. It's
>> not really about risk.
>
> Because as part of the overall huge loop discussion it has resurfaces
> how broken it is, and how it is in the way of how the loop driver works.
> Milan for example has argued for just removing it ASAP because of that,
> but I guess providing at least a bit of time of deprecation would
> be nice. Then again given that state I'd be perfectly fine with just
> removing it in 5.16 without much of a warning either.
OK fair enough, I'll queue it for 5.14.
--
Jens Axboe
prev parent reply other threads:[~2021-08-27 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 16:32 [PATCH for-5.14] cryptoloop: add a deprecation warning Christoph Hellwig
2021-08-27 16:37 ` Jens Axboe
2021-08-27 16:40 ` Christoph Hellwig
2021-08-27 16:42 ` Jens Axboe
2021-08-27 16:43 ` Christoph Hellwig
2021-08-27 16:43 ` Jens Axboe
2021-08-27 16:46 ` Christoph Hellwig
2021-08-27 16:48 ` Jens Axboe
2021-08-27 16:50 ` Christoph Hellwig
2021-08-27 16:52 ` Jens Axboe
2021-08-27 16:55 ` Christoph Hellwig
2021-08-27 16:57 ` Jens Axboe [this message]
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=e67cdaa4-7d79-7cfd-e377-d15cd62527f0@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.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