From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: [PATCH] block: default BLOCK_LEGACY_AUTOLOAD to y
Date: Fri, 25 Feb 2022 18:37:21 +0000 [thread overview]
Message-ID: <428b2fa6-68a4-79a6-3eec-74dd407e1efb@nvidia.com> (raw)
In-Reply-To: <20220225181440.1351591-1-hch@lst.de>
On 2/25/22 10:14, Christoph Hellwig wrote:
> As Luis reported, losetup currently doesn't properly create the loop
> device without this if the device node already exists because old
> scripts created it manually. So default to y for now and remove the
> aggressive removal schedule.
>
> Reported-by: Luis Chamberlain <mcgrof@kernel.org>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2022-02-25 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 18:14 [PATCH] block: default BLOCK_LEGACY_AUTOLOAD to y Christoph Hellwig
2022-02-25 18:37 ` Chaitanya Kulkarni [this message]
2022-02-25 20:31 ` Jens Axboe
2022-02-25 21:23 ` Luis Chamberlain
2022-12-28 16:55 ` Anisse Astier
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=428b2fa6-68a4-79a6-3eec-74dd407e1efb@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=mcgrof@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