From: Mark Brown <broonie@kernel.org>
To: Peter Rosin <peda@axentia.se>, Lars Povlsen <lars.povlsen@microchip.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Serge Semin <fancer.lancer@gmail.com>,
Serge Semin <Sergey.Semin@baikalelectronics.ru>,
linux-spi@vger.kernel.org
Subject: Re: [PATCH v5 0/6] spi: Adding support for Microchip Sparx5 SoC
Date: Tue, 08 Sep 2020 18:20:57 +0100 [thread overview]
Message-ID: <159958565716.16771.6460929787549553831.b4-ty@kernel.org> (raw)
In-Reply-To: <20200824203010.2033-1-lars.povlsen@microchip.com>
On Mon, 24 Aug 2020 22:30:04 +0200, Lars Povlsen wrote:
> The series add support for the Sparx5 SoC SPI controller in the
> spi-dw-mmio.c spi driver.
>
> v5 changes:
> - rx-sample-delay-ns documentation changes from Rob Herring:
> - Drop superfluous type $ref
> - Add default value = 0
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/3] spi: dw: Add support for RX sample delay register
commit: bac70b54ecb53b3d5af862dd4fcbaaad8f34ed23
[2/3] spi: dw: Add Microchip Sparx5 support
commit: 53a09635ce56e3041fb3cbc7ceef8f5de28259a5
[3/3] dt-bindings: snps, dw-apb-ssi: Add sparx5 support, plus rx-sample-delay-ns property
commit: 5ce78f4456a9b2cb103f5bad9e62636e8d086152
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
prev parent reply other threads:[~2020-09-08 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 20:30 Lars Povlsen
2020-08-24 20:30 ` [PATCH v5 1/6] spi: dw: Add support for RX sample delay register Lars Povlsen
2020-08-24 20:30 ` [PATCH v5 2/6] spi: dw: Add Microchip Sparx5 support Lars Povlsen
2020-08-24 20:30 ` [PATCH v5 3/6] arm64: dts: sparx5: Add SPI controller and associated mmio-mux Lars Povlsen
2020-08-24 20:30 ` [PATCH v5 4/6] dt-bindings: snps,dw-apb-ssi: Add sparx5 support, plus rx-sample-delay-ns property Lars Povlsen
2020-08-28 21:57 ` [PATCH v5 4/6] dt-bindings: snps, dw-apb-ssi: " Rob Herring
2020-08-24 20:30 ` [PATCH v5 5/6] arm64: dts: sparx5: Add spi-nor support Lars Povlsen
2020-08-24 20:30 ` [PATCH v5 6/6] arm64: dts: sparx5: Add spi-nand devices Lars Povlsen
2020-09-08 17:20 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=159958565716.16771.6460929787549553831.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=UNGLinuxDriver@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=peda@axentia.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®