[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACPK8Xe4TcRVBnZL7vtqGq1PTe5NEx1k4hvk4FDeYgJQ9HALFg@mail.gmail.com>
Date: Wed, 2 Dec 2020 21:19:47 +0000
From: Joel Stanley <joel@....id.au>
To: Mark Brown <broonie@...nel.org>
Cc: Boris Brezillon <bbrezillon@...nel.org>,
Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>,
Rob Herring <robh+dt@...nel.org>, linux-spi@...r.kernel.org,
devicetree <devicetree@...r.kernel.org>,
Cédric Le Goater <clg@...d.org>,
Andrew Jeffery <andrew@...id.au>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-aspeed <linux-aspeed@...ts.ozlabs.org>,
BMC-SW <BMC-SW@...eedtech.com>
Subject: Re: [v2 0/4] Porting ASPEED FMC/SPI memory controller driver
On Tue, 1 Dec 2020 at 13:58, Mark Brown <broonie@...nel.org> wrote:
>
> 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
Really? Or is there a bug in one of your scripts :)
Cheers,
Joel
>
> 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
Powered by blists - more mailing lists