[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <171984553050.67981.12522537296340689285.b4-ty@kernel.org>
Date: Mon, 01 Jul 2024 15:52:10 +0100
From: Mark Brown <broonie@...nel.org>
To: Vladimir Oltean <olteanv@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Frank Li <Frank.Li@....com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
imx@...ts.linux.dev, Kuldeep Singh <kuldeep.singh@....com>,
Vladimir Oltean <vladimir.oltean@....com>
Subject: Re: (subset) [PATCH v4 0/3] spi: fsl-dspi: Convert to yaml format
and use common SPI property
On Mon, 24 Jun 2024 14:55:26 -0400, Frank Li wrote:
> Convert fsl-dspi binding to to yaml format.
> Using common SPI property spi-cs-setup-delay-ns and spi-cs-hold-delay-ns.
> Update driver and ls1043 dts file.
>
> To: Vladimir Oltean <olteanv@...il.com>
> To: Mark Brown <broonie@...nel.org>
> To: Rob Herring <robh@...nel.org>
> To: Krzysztof Kozlowski <krzk+dt@...nel.org>
> To: Conor Dooley <conor+dt@...nel.org>
> To: Shawn Guo <shawnguo@...nel.org>
> Cc: linux-spi@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org
> Cc: devicetree@...r.kernel.org
> Cc: linux-arm-kernel@...ts.infradead.org
> Cc: imx@...ts.linux.dev
> Cc: olteanv@...il.com
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/3] spi: fsl-dspi: use common proptery 'spi-cs-setup(hold)-delay-ns'
commit: 52e78777b6bfd4bc47448791a99d5f97c82ff81c
[2/3] spi: dt-bindings: fsl-dspi: Convert to yaml format
commit: 94f19d076218a193d170da6d5ab2a87c080cc69c
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