mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "sha@pengutronix.de" <sha@pengutronix.de>
To: "Stefan Riedmüller" <S.Riedmueller@phytec.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH 2/2] mtd: nand_bbt: Skip bad blocks when searching for the BBT in NAND
Date: Wed, 14 Apr 2021 16:36:05 +0200	[thread overview]
Message-ID: <20210414143605.GX19819@pengutronix.de> (raw)
In-Reply-To: <d535d198a5eb6a8404020bbd7295e2c2ccf92182.camel@phytec.de>

0.08

Hi Stefan,

On Wed, Apr 14, 2021 at 01:18:39PM +0000, Stefan Riedmüller wrote:
> Hi Sascha,
> 
> just wanted to let you know that the kernel patch has been accepted and is
> included in the pull request for 5.13.

Thanks for the effort. I just merged it into barebox.

Sascha


> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git/log/?h=nand/for-5.13
> 
> Regards,
> Stefan
> 
> On Mon, 2021-03-29 at 07:20 +0000, Stefan Riedmüller wrote:
> > Hi Sascha,
> > 
> > here is the link to the kernel patch.
> > Sorry, I forgot to put you in cc.
> > 
> > https://patchwork.ozlabs.org/project/linux-mtd/patch/20210325102337.481172-1-s.riedmueller@phytec.de/
> > 
> > Stefan
> > 
> > On Mon, 2021-03-22 at 06:59 +0100, sha@pengutronix.de wrote:
> > > On Wed, Mar 17, 2021 at 05:14:05PM +0000, Stefan Riedmüller wrote:
> > > > Hi Sascha,
> > > > 
> > > > On Wed, 2021-03-17 at 10:41 +0100, Sascha Hauer wrote:
> > > > > Hi Stefan,
> > > > > 
> > > > > On Tue, Mar 16, 2021 at 01:36:26PM +0100, Stefan Riedmueller wrote:
> > > > > > The blocks containing the bad block table can become bad as well. So
> > > > > > make sure to skip any blocks that are marked bad when searching for
> > > > > > the
> > > > > > bad block table.
> > > > > 
> > > > > The file is a more or less direct copy from the kernel. Does the
> > > > > problem
> > > > > exist in the kernel as well?
> > > > 
> > > > From my point of view I would say yes. I have just made a small test
> > > > Issue
> > > > is
> > > > shown in the kernel as well. It is a very raw case where two BBT blocks
> > > > need
> > > > to be worn out but on the other hand this fix should not have that much
> > > > of
> > > > an
> > > > impact.
> > > > 
> > > > I will send a similar patch to the kernel.
> > > 
> > > I'd like to delay this one until it is accepted in the kernel. I do not
> > > fully understand the consequences of this patch, but hopefully on the
> > > mtd list there is someone.
> > > 
> > > Sascha
> > > 
> > _______________________________________________
> > barebox mailing list
> > barebox@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/barebox

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


  reply	other threads:[~2021-04-14 14:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 12:36 [PATCH 1/2] nand: nand-mxs: Fix marking BBT blocks as bad Stefan Riedmueller
2021-03-16 12:36 ` [PATCH 2/2] mtd: nand_bbt: Skip bad blocks when searching for the BBT in NAND Stefan Riedmueller
2021-03-17  9:41   ` Sascha Hauer
2021-03-17 17:14     ` Stefan Riedmüller
2021-03-22  5:59       ` sha
2021-03-29  7:20         ` Stefan Riedmüller
2021-04-14 13:18           ` Stefan Riedmüller
2021-04-14 14:36             ` sha [this message]
2021-04-20  6:29               ` Stefan Riedmüller
2021-05-07  7:52                 ` sha
2021-03-22  5:57 ` [PATCH 1/2] nand: nand-mxs: Fix marking BBT blocks as bad Sascha Hauer

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=20210414143605.GX19819@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=S.Riedmueller@phytec.de \
    --cc=barebox@lists.infradead.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