linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
	linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Baolin Wang <baolin.wang@linaro.org>
Subject: [GIT PULL] hwspinlock updates for v4.19
Date: Fri, 17 Aug 2018 14:45:22 -0700	[thread overview]
Message-ID: <20180817214522.GC3941@tuxbook-pro> (raw)

The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:

  Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)

are available in the Git repository at:

  git://github.com/andersson/remoteproc tags/hwlock-v4.19

for you to fetch changes up to ddb34f480d1b8051bc18e6ff22e93a6c9a33f94f:

  hwspinlock: Fix incorrect return pointers (2018-07-30 20:54:51 -0700)

----------------------------------------------------------------
hwspinlock updates for v4.19

This introduces devres helpers and an API to request a lock by name,
then migrates the sprd SPI driver to use these.

----------------------------------------------------------------
Baolin Wang (8):
      hwspinlock: Add one new API to support getting a specific hwlock by the name
      hwspinlock: Add devm_xxx() APIs to request/free hwlock
      hwspinlock: Add devm_xxx() APIs to register/unregister one hwlock controller
      hwspinlock: Remove redundant config
      hwspinlock: Fix one comment mistake
      spi: sprd: Replace of_hwspin_lock_get_id() with of_hwspin_lock_get_id_byname()
      spi: sprd: Change to use devm_hwspin_lock_request_specific()
      hwspinlock: Fix incorrect return pointers

 drivers/hwspinlock/hwspinlock_core.c | 223 ++++++++++++++++++++++++++++++++++-
 drivers/spi/spi-sprd-adi.c           |  11 +-
 include/linux/hwspinlock.h           |  37 +++++-
 3 files changed, 262 insertions(+), 9 deletions(-)

                 reply	other threads:[~2018-08-17 21:41 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=20180817214522.GC3941@tuxbook-pro \
    --to=bjorn.andersson@linaro.org \
    --cc=baolin.wang@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ohad@wizery.com \
    --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;
as well as URLs for NNTP newsgroup(s).