[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <395caa58-a8a0-4c75-85d3-4fa0f6f4a9ba@sirena.org.uk>
Date: Fri, 1 Dec 2023 18:50:15 +0000
From: Mark Brown <broonie@...nel.org>
To: Lee Jones <lee@...nel.org>
Cc: tudor.ambarus@...aro.org, pratyush@...nel.org,
miquel.raynal@...tlin.com, richard@....at, vigneshr@...com,
sbinding@...nsource.cirrus.com, james.schulman@...rus.com,
david.rhodes@...rus.com, rf@...nsource.cirrus.com, perex@...ex.cz,
tiwai@...e.com,
Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>,
linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
michael@...le.cc, linux-mtd@...ts.infradead.org,
nicolas.ferre@...rochip.com, alexandre.belloni@...tlin.com,
claudiu.beznea@...on.dev, michal.simek@....com,
linux-arm-kernel@...ts.infradead.org, alsa-devel@...a-project.org,
patches@...nsource.cirrus.com, linux-sound@...r.kernel.org,
git@....com, amitrkcian2002@...il.com
Subject: Re: (subset) [PATCH v11 01/10] mfd: tps6594: Use set/get APIs to
access spi->chip_select
On Fri, Dec 01, 2023 at 09:57:36AM +0000, Lee Jones wrote:
> On Sat, 25 Nov 2023 14:51:28 +0530, Amit Kumar Mahapatra wrote:
> > In preparation for adding multiple CS support for a device, set/get
> > functions were introduces accessing spi->chip_select in
> > 'commit 303feb3cc06a ("spi: Add APIs in spi core to set/get
> > spi->chip_select and spi->cs_gpiod")'.
> > Replace spi->chip_select with spi_get_chipselect() API.
> Applied, thanks!
> [01/10] mfd: tps6594: Use set/get APIs to access spi->chip_select
> commit: dd636638446c87c95c5beddcd367d95ac6764c6c
Is there a signed tag available for this - without this change the
subsequent SPI changes introduce a build breakage.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists