public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Elad Nachman <enachman@marvell.com>
Cc: <richard@nod.at>, <vigneshr@ti.com>, <vadym.kochan@plvision.eu>,
	<aviramd@marvell.com>, <linux-mtd@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v2] mtd: rawnand: marvell: fix layouts
Date: Mon, 5 Feb 2024 16:17:43 +0100	[thread overview]
Message-ID: <20240205161743.6c13af7b@xps-13> (raw)
In-Reply-To: <20240205134435.2769452-1-enachman@marvell.com>

Hi Elad,

enachman@marvell.com wrote on Mon, 5 Feb 2024 15:44:35 +0200:

> From: Elad Nachman <enachman@marvell.com>
> 
> The check in nand_base.c, nand_scan_tail() : has the following code:
> (ecc->steps * ecc->size != mtd->writesize) which fails for some NAND chips.
> Remove ECC entries in this driver which are not integral multiplications,
> and adjust the number of chunks for entries which fails the above
> calculation so it will calculate correctly (this was previously done
> automatically before the check and was removed in a later commit).

I don't know why linux-mtd does not collect your patches, for this time
I applied it manually to mtd/fixes.

See, linux-mtd lore link is broken, but linux-stable collected
correctly:
https://lore.kernel.org/linux-mtd/20240205134435.2769452-1-enachman@marvell.com/

Thanks,
Miquèl

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

       reply	other threads:[~2024-02-05 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240205134435.2769452-1-enachman@marvell.com>
2024-02-05 15:17 ` Miquel Raynal [this message]
     [not found] <20240103133740.1233405-1-enachman@marvell.com>
2024-02-05 12:47 ` [PATCH v2] mtd: rawnand: marvell: fix layouts Miquel Raynal

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=20240205161743.6c13af7b@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=aviramd@marvell.com \
    --cc=enachman@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=stable@vger.kernel.org \
    --cc=vadym.kochan@plvision.eu \
    --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