mirror of https://lore.kernel.org/lkml/
 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 updates for v3.13
Date: Mon, 2 Dec 2013 13:36:23 +0000	[thread overview]
Message-ID: <20131202133623.GG27568@sirena.org.uk> (raw)

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

The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:

  Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git tags/spi-v3.13-rc2

for you to fetch changes up to c18158f1fdad0de6be5386291189580484e459cf:

  Merge remote-tracking branches 'spi/fix/bcm2835', 'spi/fix/bcm63xx', 'spi/fix/mpc512x-psc', 'spi/fix/mxs', 'spi/fix/pxa2xx', 'spi/fix/qspi', 'spi/fix/rspi' and 'spi/fix/txx9' into spi-linus (2013-11-28 11:31:35 +0000)

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

spi: Fixes for v3.13

A smattering of driver specific fixes here, including a bunch for a
long standing common pattern in the error handling paths, and a fix for
an embarrassing thinko in the new devm master registration code.

----------------------------------------------------------------
Chew, Chiau Ee (1):
      spi/pxa2xx: Restore private register bits.

Mark Brown (2):
      Merge remote-tracking branch 'spi/fix/core' into spi-linus
      Merge remote-tracking branches 'spi/fix/bcm2835', 'spi/fix/bcm63xx', 'spi/fix/mpc512x-psc', 'spi/fix/mxs', 'spi/fix/pxa2xx', 'spi/fix/qspi', 'spi/fix/rspi' and 'spi/fix/txx9' into spi-linus

Mika Westerberg (1):
      spi/pxa2xx: add new ACPI IDs

Sourav Poddar (2):
      spi/qspi: cleanup pm_runtime error check.
      spi/qspi: Fix qspi remove path.

Stephen Warren (1):
      spi: core: invert success test in devm_spi_register_master

Wei Yongjun (7):
      spi: bcm2835: fix reference leak to master in bcm2835_spi_remove()
      spi: rspi: use platform drvdata correctly in rspi_remove()
      spi: mpc512x: fix reference leak to master in mpc512x_psc_spi_do_remove()
      spi: txx9: fix reference leak to master in txx9spi_remove()
      spi: bcm63xx: fix reference leak to master in bcm63xx_spi_remove()
      spi: spi-mxs: fix reference leak to master in mxs_spi_remove()
      spi/qspi: set correct platform drvdata in ti_qspi_probe()

 drivers/spi/spi-bcm2835.c     |  2 +-
 drivers/spi/spi-bcm63xx.c     |  2 +-
 drivers/spi/spi-mpc512x-psc.c |  2 +-
 drivers/spi/spi-mxs.c         |  2 +-
 drivers/spi/spi-pxa2xx.c      |  5 +++++
 drivers/spi/spi-rspi.c        |  3 +--
 drivers/spi/spi-ti-qspi.c     | 23 +++++++++++++++++++----
 drivers/spi/spi-txx9.c        |  2 +-
 drivers/spi/spi.c             |  2 +-
 9 files changed, 31 insertions(+), 12 deletions(-)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-12-02 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 13:36 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-08 10:50 [GIT PULL] spi " 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=20131202133623.GG27568@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®