All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Maxim Kochetkov <fido_max@inbox.ru>
Cc: broonie@kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR
Date: Thu, 3 Dec 2020 01:57:28 +0200	[thread overview]
Message-ID: <20201202235728.jihjacbuo2362f6v@skbuf> (raw)
In-Reply-To: <20201202142552.44385-1-fido_max@inbox.ru>

On Wed, Dec 02, 2020 at 05:25:52PM +0300, Maxim Kochetkov wrote:
> If cs-gpios property is used in devicetree then ctlr->num_chipselect value
> may be changed by spi_get_gpio_descs().
> So use ctlr->max_native_cs instead of ctlr->num_chipselect to set SPI_MCR
> 
> Fixes: 4fcc7c2292de (spi: spi-fsl-dspi: Don't access reserved fields in SPI_MCR)
> Signed-off-by: Maxim Kochetkov <fido_max@inbox.ru>
> ---

In this case, it looks like Mark did really apply it, Maxim, I'm not
sure why you resent:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git/commit/?h=for-5.10&id=2c2b3ad2c4c801bab1eec7264ea6991b1e4e8f2c

  reply	other threads:[~2020-12-02 23:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 14:25 [PATCH] spi: spi-fsl-dspi: Use max_native_cs instead of num_chipselect to set SPI_MCR Maxim Kochetkov
2020-12-02 23:57 ` Vladimir Oltean [this message]
2020-12-03  4:40   ` Maxim Kochetkov
  -- strict thread matches above, loose matches on Subject: below --
2020-12-01  8:59 Maxim Kochetkov
2020-12-01 13:57 ` Mark Brown
2020-12-02 14:20   ` Maxim Kochetkov
2020-12-02 14:22     ` Mark Brown
2020-12-02 23:55       ` Vladimir Oltean
2020-12-03  8:02         ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201202235728.jihjacbuo2362f6v@skbuf \
    --to=olteanv@gmail.com \
    --cc=broonie@kernel.org \
    --cc=fido_max@inbox.ru \
    --cc=linux-spi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.