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:52:52 -0600 [thread overview]
Message-ID: <6332d413-291c-7b1a-504e-aa69d6bf300e@kernel.dk> (raw)
In-Reply-To: <20210827165019.GB26631@lst.de>
On 8/27/21 10:50 AM, Christoph Hellwig wrote:
> On Fri, Aug 27, 2021 at 10:48:09AM -0600, Jens Axboe wrote:
>> I don't disagree with that, but that's not a new situation. Hence my
>> question on why there's this sudden mad rush to get it queued up for
>> removal, literally a few days before a kernel release.
>
> Because this allows the very useful deprecation warning to go out
> ASAP. It's not like printing a message and adding a little Kconfig
> text has any risk.
You're still not explaining why it should go asap, just that yes it will
provide this deprecation warning asap if we queue it up asap. Which is a
given.
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.
--
Jens Axboe
next prev parent reply other threads:[~2021-08-27 16:52 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 [this message]
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=6332d413-291c-7b1a-504e-aa69d6bf300e@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 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.