Hi Arseniy, avkrasnov@xxxxxxxxxxxxxx wrote on Sat, 15 Jul 2023 20:48:34 +0300: > Hello Miquel! > > On 15.07.2023 19:15, Miquel Raynal wrote: > > Hi Arseniy, > > > > AVKrasnov@xxxxxxxxxxxxxx wrote on Tue, 11 Jul 2023 15:21:26 +0300: > > > >> Hello, > >> > >> this patchset adds support for 512B ECC step size for Meson NAND. Current > >> implementation only supports 1024B. There are three patches: > >> > >> 1) Update for device tree bindings to replace 'const' type of field > >> 'nand-ecc-step-size' with 'enum' which contains 512 and 1024. > >> > >> 2) Update for device tree bindings to add dependency between properties > >> 'nand-ecc-strength' and 'nand-ecc-step-size'. > >> > >> 3) Update for Meson driver - new enum value for 512B ECC and reworked > >> ECC capabilities structure to support both 512B and 1024B ECC. By > >> default this driver uses 1024B ECC, 512B could be enabled in device > >> tree. > > > > This series does not apply correctly on nand/next, would you mind > > rebasing (nand/next on linux-mtd) and sending it again? > > Sure, as I see 0001 was applied to nand/next, so I can resend only 0002 and 0003, > as 0002 is the first patch which fails to apply? Yes indeed. > > > > > BTW the "rfc" prefix is only needed for the "first" submission, when > > you try something "new", otherwise it is no longer required. > > Ok, got it > > > > > Thanks, > > Miquèl > > Thanks, Arseniy Thanks, Miquèl
