linux-kernel.vger.kernel.org archive mirror
 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 fixes v5.1-rc3
Date: Sun, 31 Mar 2019 08:11:35 +0530	[thread overview]
Message-ID: <20190331024135.GA2937@vkoul-mobl> (raw)

Hi Linus,

Here is the pull request fro v5.1-rc3. This includes revery of patch due
to reported regression and fix on MAINTAINER file for uniphier-mdmac.c
file path.

The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:

  Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)

are available in the Git repository at:

  git://git.infradead.org/users/vkoul/slave-dma.git tags/dmaengine-fix-5.1-rc3

for you to fetch changes up to d498bc0ce8acb4a1bb80d6089d1932d919dc2532:

  MAINTAINERS: Fix uniphier-mdmac.c file path (2019-03-26 10:55:47 +0530)

----------------------------------------------------------------
dmaengine-5.10-rc3

dmaengine fixes for v5.10-rc3

 - Revert dmaengine: stm32-mdma: Add a check on read_u32_array as that
   caused regression
 - Fix MAINTAINER file uniphier-mdmac.c file path

----------------------------------------------------------------
Pierre-Yves MORDRET (1):
      dmaengine: stm32-mdma: Revert "dmaengine: stm32-mdma: Add a check on read_u32_array"

Vinod Koul (1):
      MAINTAINERS: Fix uniphier-mdmac.c file path

 MAINTAINERS              | 2 +-
 drivers/dma/stm32-mdma.c | 4 +---
 2 files changed, 2 insertions(+), 4 deletions(-)

Thanks
-- 
~Vinod

             reply	other threads:[~2019-03-31  2:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-31  2:41 Vinod Koul [this message]
2019-03-31 16:00 ` [GIT PULL]: dmaengine fixes v5.1-rc3 pr-tracker-bot

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=20190331024135.GA2937@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;
as well as URLs for NNTP newsgroup(s).