public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: hch <hch@lst.de>
To: Richard Weinberger <richard@nod.at>
Cc: hch <hch@lst.de>,
	joern@lazybastard.org, Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtd/block2mtd: don't poke into block layer internals
Date: Tue, 19 Oct 2021 07:53:09 +0200	[thread overview]
Message-ID: <20211019055309.GA20805@lst.de> (raw)
In-Reply-To: <1862961222.73085.1634239699925.JavaMail.zimbra@nod.at>

On Thu, Oct 14, 2021 at 09:28:19PM +0200, Richard Weinberger wrote:
> > instead.  Note that this contains a small behavior change in that erase
> > now unconditionally writes all Fs instead of first scanning for them.
> 
> Unless you have a strong opinoin I'd like to keep the scanning.
> The original use case of block2mtd is using Compact Flash (ATA)
> as MTD. Some of this devices are super stupid and I fear the 0xFF scanning
> is here to avoid programming 0xFF bytes into the NAND.
> Just to be on the safe side...

I played with keeping the scanning, but it really is a mess.  Shouldn't
the higher layers (ubi, jffs2, etc) know what has already been erased?

Btw, Joerns address bounces.  Does anyone knw if he still wants to
maintain block2mtd and has a new address or if he should be removed from
the maintainers list?

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2021-10-19  5:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 14:52 RFC: decouple block2mtd from block layer internals Christoph Hellwig
2021-10-14 14:52 ` [PATCH] mtd/block2mtd: don't poke into " Christoph Hellwig
2021-10-14 19:28   ` Richard Weinberger
2021-10-15  6:28     ` hch
2021-10-15  6:53       ` Miquel Raynal
2021-10-19  5:53     ` hch [this message]
2021-10-22  7:50       ` Richard Weinberger

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=20211019055309.GA20805@lst.de \
    --to=hch@lst.de \
    --cc=joern@lazybastard.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    /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