Message ID | cover.1705348269.git.u.kleine-koenig@pengutronix.de |
---|---|
Headers | show |
Series | spi: get rid of some legacy macros | expand |
On Mon, Jan 15, 2024 at 09:12:46PM +0100, Uwe Kleine-König wrote: > In commit 8caab75fd2c2 ("spi: Generalize SPI "master" to "controller"") > some functions were renamed. Further some compat defines were introduced > to map the old names to the new ones. > Patch #18 and #19 touch the same driver, otherwise the patches #1 - #31 > are pairwise independent and could be applied by their respective > maintainers. The alternative is to let all patches go via the spi tree. > Mark, what's your preference here? I don't have a strong preference here, I'm happy to take all the patches if the maintainers for the other subsystem are OK with that - ideally I'd apply things at -rc1 but the timeline is a bit tight there. I think my plan here unless anyone objects (or I notice something myself) will be to queue things at -rc3, please shout if that doesn't seem reasonable.
Hello Mark, On Tue, Jan 16, 2024 at 02:40:39PM +0000, Mark Brown wrote: > On Mon, Jan 15, 2024 at 09:12:46PM +0100, Uwe Kleine-König wrote: > > > In commit 8caab75fd2c2 ("spi: Generalize SPI "master" to "controller"") > > some functions were renamed. Further some compat defines were introduced > > to map the old names to the new ones. > > > Patch #18 and #19 touch the same driver, otherwise the patches #1 - #31 > > are pairwise independent and could be applied by their respective > > maintainers. The alternative is to let all patches go via the spi tree. > > Mark, what's your preference here? > > I don't have a strong preference here, I'm happy to take all the patches > if the maintainers for the other subsystem are OK with that - ideally > I'd apply things at -rc1 but the timeline is a bit tight there. I think > my plan here unless anyone objects (or I notice something myself) will > be to queue things at -rc3, please shout if that doesn't seem > reasonable. From my side there is no rush, we lived with these defines since 4.13-rc1. Applying them during the next merge window is fine for me. Anyhow, I intend to resend the series for the feedback I received after -rc1. Up to you when you want to apply it. Watching out for offending patches using lore shouldn't be a big thing and I can do that. Best regards Uwe