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-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
        Abe Kohandel <abe.kohandel@intel.com>
Cc:     Serge Semin <fancer.lancer@gmail.com>,
        Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>,
        Andy Shevchenko <andriy.shevchenko@linux.intel.com>
In-Reply-To: <20230613162103.569812-1-abe.kohandel@intel.com>
References: <20230613162103.569812-1-abe.kohandel@intel.com>
Subject: Re: [PATCH] spi: dw: Replace incorrect spi_get_chipselect with set
Message-Id: <168668716790.174856.4659003414906953886.b4-ty@kernel.org>
Date:   Tue, 13 Jun 2023 21:12:47 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 13 Jun 2023 09:21:03 -0700, Abe Kohandel wrote:
> Commit 445164e8c136 ("spi: dw: Replace spi->chip_select references with
> function calls") replaced direct access to spi.chip_select with
> spi_*_chipselect calls but incorrectly replaced a set instance with a
> get instance, replace the incorrect instance.
> 
> 

Applied to

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

Thanks!

[1/1] spi: dw: Replace incorrect spi_get_chipselect with set
      commit: eee43699217504ba69cadefc85c6992df555e33f

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