Message ID | 20220127091808.1043392-1-miquel.raynal@bootlin.com (mailing list archive) |
---|---|
Headers | show |
Series | External ECC engines & Macronix support | expand |
On Thu, Jan 27, 2022 at 10:17:55AM +0100, Miquel Raynal wrote: > Hello all, > > I've applied the beginning of the series (bindings + ECC part) in a > branch named spi-mem-ecc on the MTD korg repository. I already applied > this second halve on top of the spi-mem-ecc branch but there was a > misunderstanding and they ended up not being fully reviewed. Hence here > there are once again, there are no changes since v9 beside the rebase. This looks good, please send a pull request. In general for future reference if there's patches for one of my subsystems that I've not explicitly commented on I'm probably expecting to apply them.
Hi Mark, broonie@kernel.org wrote on Thu, 27 Jan 2022 19:56:50 +0000: > On Thu, Jan 27, 2022 at 10:17:55AM +0100, Miquel Raynal wrote: > > Hello all, > > > > I've applied the beginning of the series (bindings + ECC part) in a > > branch named spi-mem-ecc on the MTD korg repository. I already applied > > this second halve on top of the spi-mem-ecc branch but there was a > > misunderstanding and they ended up not being fully reviewed. Hence here > > there are once again, there are no changes since v9 beside the rebase. > > This looks good, please send a pull request. Great thanks! > In general for future reference if there's patches for one of my > subsystems that I've not explicitly commented on I'm probably expecting > to apply them. Oh yeah this is very clear, but as this series heavily depends on some core MTD changes as well, it was decided that everything would be merged in one operation and that's why I started constructing the spi-mem-ecc branch, which touches four different 'cores': nand, spi-nand, spi, spi-mem. Because of the last minute reviews right before the beginning of the merge window I decided not to apply the second halve of the series too quickly and delayed the whole patchset including the previous patches which had no interest on their own. > On Fri, Nov 26, 2021 at 03:10:59PM +0100, Miquel Raynal wrote: > > > If you acknowledge the SPI bits I believe I can carry the entire series > > through the MTD tree. If you fear conflicts and need an immutable tag I > > can also do that. > > It'd be good to have the tag just in case, there's generally a lot of > work in this area. > > Reviewed-by: Mark Brown <broonie@kernel.org> As three patches in this series were new/reworked I dropped your tag there. I should have asked you again. Shall I add them (back) to the following patches? spi: cadence-quadspi: Provide a capability structure spi: mxic: Provide a capability structure spi: spi-mem: Introduce a capability structure Thanks, Miquèl
On Fri, Jan 28, 2022 at 09:08:12AM +0100, Miquel Raynal wrote: > As three patches in this series were new/reworked I dropped your tag > there. I should have asked you again. Shall I add them (back) to the > following patches? > spi: cadence-quadspi: Provide a capability structure > spi: mxic: Provide a capability structure > spi: spi-mem: Introduce a capability structure Yes, please.
Hi Mark, broonie@kernel.org wrote on Fri, 28 Jan 2022 22:34:52 +0000: > On Fri, Jan 28, 2022 at 09:08:12AM +0100, Miquel Raynal wrote: > > > As three patches in this series were new/reworked I dropped your tag > > there. I should have asked you again. Shall I add them (back) to the > > following patches? > > > spi: cadence-quadspi: Provide a capability structure > > spi: mxic: Provide a capability structure > > spi: spi-mem: Introduce a capability structure > > Yes, please. Great, thanks. I'll apply v10 soon, and will share an immutable tag. Thanks, Miquèl