Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Mark Brown <broonie@kernel.org>
To:     amit.kumar-mahapatra@xilinx.com
Cc:     linux-kernel@vger.kernel.org, michal.simek@xilinx.com,
        linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
        git@xilinx.com
In-Reply-To: <20220512145820.20425-1-amit.kumar-mahapatra@xilinx.com>
References: <20220512145820.20425-1-amit.kumar-mahapatra@xilinx.com>
Subject: Re: [PATCH] spi: spi-zynqmp-gqspi: Add two chip select support
Message-Id: <165459879429.302078.13267893267335834216.b4-ty@kernel.org>
Date:   Tue, 07 Jun 2022 11:46:34 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 12 May 2022 20:28:20 +0530, Amit Kumar Mahapatra wrote:
> ZynqMP GQSPI controller can support up to two chip selects but the current
> GQSPI driver only support CS0. With this update and num-cs DT property set
> to 2 GQSPI driver can now support two slave devices each connected to one
> chip select.
> 
> GQSPI driver configures the Lower CS and Upper CS based on the reg DT
> property.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-zynqmp-gqspi: Add two chip select support
      commit: dd9c232d47277960aba0c603c87a1cfd85d69438

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