Linux block layer
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, linux-block@vger.kernel.org
Subject: Re: [PATCH for-5.14] cryptoloop: add a deprecation warning
Date: Fri, 27 Aug 2021 18:46:37 +0200	[thread overview]
Message-ID: <20210827164637.GA26631@lst.de> (raw)
In-Reply-To: <c7e538b3-e669-1963-b6c5-475285e96784@kernel.dk>

On Fri, Aug 27, 2021 at 10:43:53AM -0600, Jens Axboe wrote:
> On 8/27/21 10:43 AM, Christoph Hellwig wrote:
> > On Fri, Aug 27, 2021 at 10:42:59AM -0600, Jens Axboe wrote:
> >> But what's the point? Why not just wait for 5.15, it's not like we're
> >> in a mad dash to get it removed.
> > 
> > Actually we kinda are :)
> 
> Because?

It causes trouble by interacting with the actual loop driver people
use in really weird ways, while beeing broken and not actually supported
by userspace tools for about a decade.

  reply	other threads:[~2021-08-27 16:46 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 [this message]
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

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=20210827164637.GA26631@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --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