Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     gch981213@gmail.com, linux-spi@vger.kernel.org
Cc:     cai.huoqing@linux.dev, paul@crapouillou.net, richard@nod.at,
        krzk+dt@kernel.org, yukuai3@huawei.com, colin.king@intel.com,
        linux-kernel@vger.kernel.org, matthias.bgg@gmail.com,
        vigneshr@ti.com, linux-mtd@lists.infradead.org,
        f.fainelli@gmail.com, p.yadav@ti.com, tsbogend@alpha.franken.de,
        robh+dt@kernel.org, devicetree@vger.kernel.org,
        linux-mediatek@lists.infradead.org, rogerq@kernel.org,
        linux-arm-kernel@lists.infradead.org, miquel.raynal@bootlin.com,
        wsa+renesas@sang-engineering.com
In-Reply-To: <20220424032527.673605-1-gch981213@gmail.com>
References: <20220424032527.673605-1-gch981213@gmail.com>
Subject: Re: (subset) [PATCH v6 0/5] spi: add support for Mediatek SPI-NAND controller
Message-Id: <165109719250.501011.1358501844817783587.b4-ty@kernel.org>
Date:   Wed, 27 Apr 2022 23:06:32 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Sun, 24 Apr 2022 11:25:22 +0800, Chuanhong Guo wrote:
> Mediatek has an extended version of their NAND Flash Interface which
> has a SPI-NAND mode. In this mode, the controller can perform 1-bit
> spi-mem ops for up-to 0xa0 bytes and typical SPI-NAND single, dual
> and quad IO page cache ops with 2-byte address. Additionally, the
> page cache ops can be performed with ECC and auto data formatting
> using the ECC engine of the controller.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[2/5] spi: add driver for MTK SPI NAND Flash Interface
      commit: 764f1b7481645b2b4488eda26c4da7f331697e6b
[4/5] spi: dt-bindings: add binding doc for spi-mtk-snfi
      commit: 69bb9b29bf67e850beece45e9c99ca707eac7e41

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark