Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     linux-spi@vger.kernel.org,
        Tharun Kumar P <tharunkumar.pasumarthi@microchip.com>
Cc:     linux-kernel@vger.kernel.org
In-Reply-To: <20230404171613.1336093-1-tharunkumar.pasumarthi@microchip.com>
References: <20230404171613.1336093-1-tharunkumar.pasumarthi@microchip.com>
Subject: Re: [PATCH SPI for-next 0/3] spi: mchp-pci1xxxx: Fix minor bugs in
 spi-pci1xxxx driver
Message-Id: <168070221494.64941.1088443931679332208.b4-ty@kernel.org>
Date:   Wed, 05 Apr 2023 14:43:34 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 04 Apr 2023 22:46:10 +0530, Tharun Kumar P wrote:
> This patch series fixes the following bugs in spi-pci1xxxx driver:
> 1. Length of SPI transactions is improper
> 2. SPI transactions fail after suspend and resume
> 3. Incorrect implementation of pci1xxxx_spi_set_cs API
> 
> Tharun Kumar P (3):
>   spi: mchp-pci1xxxx: Fix length of SPI transactions not set properly in
>     driver
>   spi: mchp-pci1xxxx: Fix SPI transactions not working after suspend and
>     resume
>   spi: mchp-pci1xxxx: Fix improper implementation of disabling chip
>     select lines
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/3] spi: mchp-pci1xxxx: Fix length of SPI transactions not set properly in driver
      commit: 35c8c5e503a82e0a4bf251d32096211eba8c2be6
[2/3] spi: mchp-pci1xxxx: Fix SPI transactions not working after suspend and resume
      commit: 4266d21669de62cf3fb6774f7d404c1eb95a5ab3
[3/3] spi: mchp-pci1xxxx: Fix improper implementation of disabling chip select lines
      commit: 45d2af82e0e6f662d0d0db20993b35cb1d8da646

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