public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Sowjanya Komatineni <skomatineni@nvidia•com>
Subject: linux-next: Fixes tags need some work in the spi-fixes tree
Date: Tue, 2 Apr 2019 04:58:28 +1100	[thread overview]
Message-ID: <20190402045828.699f5700@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]

Hi Mark,

In commit

  019194933339 ("spi: tegra114: reset controller on probe")

Fixes tag

  Fixes: SPI driver can be built as module so perform SPI controller reset

has these problem(s):

  - No SHA1 recognised

In commit

  f4ce428c41fb ("spi: tegra114: configure dma burst size to fifo trig level")

Fixes tag

  Fixes: Configure DMA burst size to be same as SPI TX/RX trigger levels

has these problem(s):

  - No SHA1 recognised

In commit

  c4fc9e5b28ff ("spi: tegra114: flush fifos")

Fixes tag

  Fixes: Flush TX and RX FIFOs before start of new transfer and on FIFO

has these problem(s):

  - No SHA1 recognised

In commit

  32bd1a9551ca ("spi: tegra114: terminate dma and reset on transfer timeout")

Fixes tag

  Fixes: terminate DMA and perform controller reset on transfer timeout

has these problem(s):

  - No SHA1 recognised

In commit

  1a89ac5b9189 ("spi: tegra114: fix for unpacked mode transfers")

Fixes tag

  Fixes: computation of actual bytes to fill/receive in/from FIFO in unpacked

has these problem(s):

  - No SHA1 recognised

In commit

  7b3d10cdf54b ("spi: tegra114: clear packed bit for unpacked mode")

Fixes tag

  Fixes: Clear packed bit when not using packed mode.

has these problem(s):

  - No SHA1 recognised

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2019-04-01 17:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190402045828.699f5700@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=broonie@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=skomatineni@nvidia$(echo .)com \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox