linux-kernel - Re: [v2 0/4] Porting ASPEED FMC/SPI memory controller driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <160683107674.35139.14509237313835347013.b4-ty@kernel.org>
Date:   Tue, 01 Dec 2020 13:57:56 +0000
From:   Mark Brown <broonie@...nel.org>
To:     bbrezillon@...nel.org,
        Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>,
        robh+dt@...nel.org, joel@....id.au, linux-spi@...r.kernel.org,
        devicetree@...r.kernel.org, clg@...d.org, andrew@...id.au,
        linux-kernel@...r.kernel.org, linux-aspeed@...ts.ozlabs.org
Cc:     BMC-SW@...eedtech.com
Subject: Re: [v2 0/4] Porting ASPEED FMC/SPI memory controller driver

On Tue, 3 Nov 2020 15:21:58 +0800, Chin-Ting Kuo wrote:
> This patch series aims to porting ASPEED FMC/SPI memory controller
> driver with spi-mem interface. Adjust device tree setting of SPI NOR
> flash in order to fit real AST2600 EVB and new SPI memory controller
> driver. Also, this patch has been verified on AST2600-A1 EVB.
> 
> v2: Fix sparse warnings reported by kernel test robot <lkp@...el.com>.
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: spi: Add binding file for ASPEED FMC/SPI memory controller
      (no commit info)
[2/2] spi: aspeed: Add ASPEED FMC/SPI memory controller driver
      (no commit info)

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