Re: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR

Subject: Re: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
From: Mark Brown <broonie@xxxxxxxxxx>
Date: Wed, 2 Dec 2020 14:22:20 +0000
Cc: olteanv@xxxxxxxxx, linux-spi@xxxxxxxxxxxxxxx
In-reply-to: <e19002f8-a8a8-6201-6680-ef0b586c6367@inbox.ru>
References: <20201201085916.63543-1-fido_max@inbox.ru> <160683107678.35139.1439064414776102118.b4-ty@kernel.org> <e19002f8-a8a8-6201-6680-ef0b586c6367@inbox.ru>
User-agent: Mutt/1.10.1 (2018-07-13)

On Wed, Dec 02, 2020 at 05:20:00PM +0300, Maxim Kochetkov wrote:

> Should I resend it?

If the patch isn't actually applied then yes.

Attachment: signature.asc
Description: PGP signature

Follow-Ups:
- Re: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
  - From: Vladimir Oltean

References:
- [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
  - From: Maxim Kochetkov
- Re: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
  - From: Mark Brown
- Re: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
  - From: Maxim Kochetkov