Message ID | 20230606145402.474866-1-abe.kohandel@intel.com (mailing list archive) |
---|---|
Headers | show |
Series | spi: dw: Add compatible for Intel Mount Evans SoC | expand |
On Tue, 06 Jun 2023 07:54:00 -0700, Abe Kohandel wrote: > The Intel Mount Evans SoC's Integrated Management Complex has a DW > apb_ssi_v4.02a controller. This series adds support for this controller. > > No SoC level chip select override is provided and as such no DMA > configuration is done for the controller. > > Thanks, > Abe > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/2] spi: dw: Add compatible for Intel Mount Evans SoC commit: 0760d5d0e9f0c0e2200a0323a61d1995bb745dee [2/2] dt-bindings: spi: snps,dw-apb-ssi: Add compatible for Intel Mount Evans SoC commit: 7bac98a338d63efb0b44ce4b79d53838491f00df 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
On Tue, Jun 06, 2023 at 05:24:36PM +0100, Mark Brown wrote: > On Tue, 06 Jun 2023 07:54:00 -0700, Abe Kohandel wrote: > > The Intel Mount Evans SoC's Integrated Management Complex has a DW > > apb_ssi_v4.02a controller. This series adds support for this controller. > > > > No SoC level chip select override is provided and as such no DMA > > configuration is done for the controller. > > > > Thanks, > > Abe > > > > [...] > > Applied to > > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Mark, next time please wait at least for a few days before applying. Give me a chance to review.) * In this case I have had a question regarding the in-code comment which may have been needed to be fixed a bit. -Serge(y) > > Thanks! > > [1/2] spi: dw: Add compatible for Intel Mount Evans SoC > commit: 0760d5d0e9f0c0e2200a0323a61d1995bb745dee > [2/2] dt-bindings: spi: snps,dw-apb-ssi: Add compatible for Intel Mount Evans SoC > commit: 7bac98a338d63efb0b44ce4b79d53838491f00df > > 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 >
On Tue, Jun 06, 2023 at 07:40:40PM +0300, Serge Semin wrote: > Mark, next time please wait at least for a few days before applying. > Give me a chance to review.) It's a trivial quirk for a platform, it seemed more hassle to wait TBH. > * In this case I have had a question regarding the in-code comment > which may have been needed to be fixed a bit. That can always be fixed incrementally if there's issues.
On Tue, Jun 06, 2023 at 05:47:40PM +0100, Mark Brown wrote: > On Tue, Jun 06, 2023 at 07:40:40PM +0300, Serge Semin wrote: > > > Mark, next time please wait at least for a few days before applying. > > Give me a chance to review.) > > It's a trivial quirk for a platform, it seemed more hassle to wait TBH. > > > * In this case I have had a question regarding the in-code comment > > which may have been needed to be fixed a bit. > > That can always be fixed incrementally if there's issues. Ok. I've sent my comment in that regards. Let's see what the author responds. -Serge(y)