[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162075727215.18180.8620014243960066654.b4-ty@kernel.org>
Date: Tue, 11 May 2021 19:21:27 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-arm-kernel@...ts.infradead.org, alsa-devel@...a-project.org
Cc: Mark Brown <broonie@...nel.org>,
Haojian Zhuang <haojian.zhuang@...il.com>,
Takashi Iwai <tiwai@...e.com>, Daniel Mack <daniel@...que.org>,
Robert Jarzmik <robert.jarzmik@...e.fr>,
Liam Girdwood <lgirdwood@...il.com>
Subject: Re: (subset) [PATCH v3 00/14] spi: pxa2xx: Set of cleanups
On Mon, 10 May 2021 15:41:20 +0300, Andy Shevchenko wrote:
> Set of cleanups here and there related to the SPI PXA2xx driver.
> On top of them, adding the special type for Intel Merrifield.
>
> In v3:
> - rebased on top of v5.13-rc1 and/or spi/for-5,14
>
> In v2:
> - cover letter (Mark)
> - drop moving the header in patch 5 (Mark)
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[07/14] spi: pxa2xx: Introduce int_stop_and_reset() helper
commit: ab77fe8935c57d1339d3df64957f32e87f0d5ef3
[08/14] spi: pxa2xx: Reuse int_error_stop() in pxa2xx_spi_slave_abort()
commit: 4761d2e7e51cfbe6fdb4e95903d407927f519f50
[09/14] spi: pxa2xx: Use pxa_ssp_enable()/pxa_ssp_disable() in the driver
commit: 0c8ccd8b267fc735e4621774ce62728f27d42863
[10/14] spi: pxa2xx: Extract pxa2xx_spi_update() helper
commit: 1bed378c6b9116c51ae59b970cf3d9b4e9e62ced
[11/14] spi: pxa2xx: Extract clear_SSCR1_bits() helper
commit: 42c80cd439a938569a86f6ae135d38c1cda5569b
[12/14] spi: pxa2xx: Extract read_SSSR_bits() helper
commit: 6d380132eaea536bef641f21847c8a7987e96ad8
[13/14] spi: pxa2xx: Constify struct driver_data parameter
commit: eca32c3974c0664f88fed90b327f473bd18a4809
[14/14] spi: pxa2xx: Introduce special type for Merrifield SPIs
commit: 3fdb59cf10b020b32b9f1dfc78611320623dcb3e
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