diff options
| author | Christoph Hellwig <hch@lst.de> | 2022-02-25 19:14:40 +0100 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2022-02-27 14:49:23 -0700 |
| commit | 451f0b6f4c44d7b649ae609157b114b71f6d7875 (patch) | |
| tree | 19e10226c0541f8fca6b749533b69e2e4f89092c /drivers/mfd/max8998.c | |
| parent | 86d7331299fda7634b11c1b7c911432679d525a5 (diff) | |
| download | linux-451f0b6f4c44d7b649ae609157b114b71f6d7875.tar.gz | |
block: default BLOCK_LEGACY_AUTOLOAD to y
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>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Link: https://lore.kernel.org/r/20220225181440.1351591-1-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/mfd/max8998.c')
0 files changed, 0 insertions, 0 deletions