All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tudor Ambarus <Tudor.Ambarus@microchip.com>,
	Pratyush Yadav <p.yadav@ti.com>, Michael Walle <michael@walle.cc>,
	MTD Maling List <linux-mtd@lists.infradead.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH] mtd: Introduce an expert mode for forensics and debugging purposes
Date: Mon, 10 Jan 2022 16:01:13 +0100	[thread overview]
Message-ID: <20220110160113.751eda38@xps13> (raw)
In-Reply-To: <CAMuHMdVgAnfLTkbb7GP2BZMAOtwBkjn9Knfupie5Kpaq=rOcOA@mail.gmail.com>

Hi Geert,

geert@linux-m68k.org wrote on Mon, 10 Jan 2022 15:57:49 +0100:

> Hi Miquèl,
> 
> On Mon, Jan 10, 2022 at 3:41 PM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> > geert@linux-m68k.org wrote on Mon, 10 Jan 2022 14:15:27 +0100:  
> > > On Thu, Nov 18, 2021 at 12:47 PM Miquel Raynal
> > > <miquel.raynal@bootlin.com> wrote:  
> > > > When developping NAND controller drivers or when debugging filesystem
> > > > corruptions, it is quite common to need hacking locally into the
> > > > MTD/NAND core in order to get access to the content of the bad
> > > > blocks. Instead of having multiple implementations out there let's
> > > > provide a simple yet effective specific MTD-wide debugfs entry to fully
> > > > disable these checks on purpose.
> > > >
> > > > A warning is added to inform the user when this mode gets enabled.
> > > >
> > > > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>  
> > >
> > > Thanks for your patch, which is now commit 67b967ddd93d0ed5 ("mtd:
> > > Introduce an expert mode for forensics and debugging purposes")
> > > in mtd/next.  
> >
> > Thanks for reviewing! Unfortunately I've sent the MTD pull-request to
> > Linus this morning so I'll have to address this in subsequent
> > commits.  
> 
> Np, as long as no out-of-tree modules start using these symbols ;-)
> 
> This is just one of the things I noticed right before the Xmas and
> NY holidays, but didn't get to reporting or fixing before...

BTW if you want to contribute this change you're welcome, otherwise
I'll do it when I have a bit of time.

Thanks,
Miquèl

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

  reply	other threads:[~2022-01-10 15:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 11:46 [PATCH] mtd: Introduce an expert mode for forensics and debugging purposes Miquel Raynal
2021-12-03 13:37 ` Miquel Raynal
2022-01-10 13:15 ` Geert Uytterhoeven
2022-01-10 14:41   ` Miquel Raynal
2022-01-10 14:57     ` Geert Uytterhoeven
2022-01-10 15:01       ` Miquel Raynal [this message]
2022-01-27 10:46   ` Miquel Raynal
2022-01-27 11:07     ` Geert Uytterhoeven
2022-01-27 11:18       ` Miquel Raynal
2022-01-27 11:57         ` Geert Uytterhoeven

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=20220110160113.751eda38@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=p.yadav@ti.com \
    --cc=richard@nod.at \
    --cc=thomas.petazzoni@bootlin.com \
    --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 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.