The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dma <dmaengine@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL]: dmaengine updates for v4.17-rc6
Date: Sat, 19 May 2018 20:24:37 +0530	[thread overview]
Message-ID: <20180519145437.GA6437@vkoul-mobl> (raw)

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

Hi Linus,

Here is dmaengine request. Please PULL to receive qcom bam dam runtime pm fix
and email update for me. So I have moved and would be using kernel.org id.
My PGP keys are also updated, let me know if anything is not right...

The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:

  Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)

are available in the Git repository at:

  git://git.infradead.org/users/vkoul/slave-dma.git tags/dmaengine-fix-4.17-rc6

for you to fetch changes up to dbad41e7bb5f4b9949ff5ea1d76c20711f326308:

  dmaengine: qcom: bam_dma: check if the runtime pm enabled (2018-05-17 16:16:49 +0530)

----------------------------------------------------------------
dmaengine fix for 4.17-rc6

 - qcom bam runtime_pm fix
 - My email update

----------------------------------------------------------------
Srinivas Kandagatla (1):
      dmaengine: qcom: bam_dma: check if the runtime pm enabled

Vinod Koul (1):
      dmaengine: Update email address for Vinod

 MAINTAINERS                |  2 +-
 drivers/dma/qcom/bam_dma.c | 18 +++++++++++++-----
 2 files changed, 14 insertions(+), 6 deletions(-)

Thanks
-- 
~Vinod

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

                 reply	other threads:[~2018-05-19 14: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=20180519145437.GA6437@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@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