All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: [GIT PULL] SPI fixes for v4.20
Date: Wed, 28 Nov 2018 15:54:04 +0000	[thread overview]
Message-ID: <20181128155404.GJ6828@sirena.org.uk> (raw)

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

The following changes since commit 0c903aafc8529f64d24d2cd6df32f2bf16aad20b:

  spi: lpspi: add imx8qxp compatible string (2018-10-21 16:55:23 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git spi-fix-v4.20-rc4

for you to fetch changes up to 91b9deefedf4c35a01027ce38bed7299605026a3:

  spi: omap2-mcspi: Add missing suspend and resume calls (2018-11-15 16:20:43 -0800)

----------------------------------------------------------------
spi: Fixes for v4.20

A few driver specific fixes here, nothing big or that stands out for
anyone other than the driver users.

----------------------------------------------------------------

Forgot to note that the mcspi thing is a fix for issues that started
showing up with a change in defconfig in this release to make cpuidle
get turned on by default.

Keiji Hayashibara (1):
      spi: uniphier: fix incorrect property items

Leilk Liu (1):
      spi: mediatek: use correct mata->xfer_len when in fifo transfer

Tony Lindgren (1):
      spi: omap2-mcspi: Add missing suspend and resume calls

 .../devicetree/bindings/spi/spi-uniphier.txt       | 14 ++++----
 drivers/spi/spi-mt65xx.c                           |  4 +--
 drivers/spi/spi-omap2-mcspi.c                      | 37 +++++++++++++++-------
 3 files changed, 35 insertions(+), 20 deletions(-)

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

                 reply	other threads:[~2018-11-28 15:54 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=20181128155404.GJ6828@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.