[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173092571984.200222.14602988312951678347.b4-ty@kernel.org>
Date: Wed, 06 Nov 2024 20:41:59 +0000
From: Mark Brown <broonie@...nel.org>
To: Hector Martin <marcan@...can.st>, Sven Peter <sven@...npeter.dev>,
Alyssa Rosenzweig <alyssa@...enzweig.io>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Janne Grunau <j@...nau.net>
Cc: asahi@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Nick Chan <towinchenmi@...il.com>,
Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: (subset) [PATCH v4 0/3] Apple SPI controller driver
On Tue, 05 Nov 2024 09:08:28 +0100, Janne Grunau wrote:
> This updated series address the review comments from the original
> submission in 2021 [1]. It adds a new SPI controller driver for Apple
> SoCs and is based on spi-sifive. It has been tested with the generic
> jedec,spi-nor support and with a downstream driver for an Apple specific
> HID over SPI transport.
>
> As usual, I'm splitting off the MAINTAINERS and DT binding changes.
> We would rather merge the MAINTAINERS change through the Asahi-SoC
> tree to avoid merge conflicts as things trickle upstream, since
> we have other submissions touching that section of the file.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/3] dt-bindings: spi: apple,spi: Add binding for Apple SPI controllers
(no commit info)
[2/3] spi: apple: Add driver for Apple SPI controller
commit: c36212b2610d09eb42142beb0d5613c70206c658
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