[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1691046252.219046.1668109493753.JavaMail.zimbra@nod.at>
Date: Thu, 10 Nov 2022 20:44:53 +0100 (CET)
From: Richard Weinberger <richard@....at>
To: Daniel Golle <daniel@...rotopia.org>
Cc: Jens Axboe <axboe@...nel.dk>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Vignesh Raghavendra <vigneshr@...com>,
Davidlohr Bueso <dave@...olabs.net>,
Matthew Wilcox <willy@...radead.org>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Chaitanya Kulkarni <kch@...dia.com>,
Ming Lei <ming.lei@...hat.com>,
linux-block <linux-block@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-mtd <linux-mtd@...ts.infradead.org>,
linux-efi <linux-efi@...r.kernel.org>
Subject: Re: [PATCH v4 4/5] mtd_blkdevs: add option to enable scanning for
partitions
----- Ursprüngliche Mail -----
> Von: "Daniel Golle" <daniel@...rotopia.org>
> +
> + if (!IS_ENABLED(CONFIG_MTD_BLOCK_PARTITIONS) || mtd_type_is_nand(new->mtd))
> + gd->flags |= GENHD_FL_NO_PART;
I know that NAND should not get used with mtdblock because lack of wearleveling and
in general too many writes. But what exactly is the rationale to deny part scanning for NAND?
Thanks,
//richard
Powered by blists - more mailing lists