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.18-rc4
Date: Sat, 7 Jul 2018 17:46:13 +0530 [thread overview]
Message-ID: <20180707121613.GY22377@vkoul-mobl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
Heya Linus,
We have few odd fixes on driver and one email update change for you this
time. Please Pull to receive:
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://git.infradead.org/users/vkoul/slave-dma.git tags/dmaengine-fix-4.18-rc4
for you to fetch changes up to c4c2b7644cc9a41f17a8cc8904efe3f66ae4c7ed:
dmaengine: k3dma: Off by one in k3_of_dma_simple_xlate() (2018-06-28 11:57:21 +0530)
----------------------------------------------------------------
dmaengine fixes for v4.18-rc4
- Driver fixes for k3dma (off by one), pl330 (burst residue granularity)
and omap-dma (incorrect residue_granularity)
- Sinan's email update
----------------------------------------------------------------
Dan Carpenter (1):
dmaengine: k3dma: Off by one in k3_of_dma_simple_xlate()
Janusz Krzysztofik (1):
dmaengine: ti: omap-dma: Fix OMAP1510 incorrect residue_granularity
Marek Szyprowski (1):
dmaengine: pl330: report BURST residue granularity
Sinan Kaya (1):
MAINTAINERS: Update email-id of Sinan Kaya
MAINTAINERS | 2 +-
drivers/dma/k3dma.c | 2 +-
drivers/dma/pl330.c | 2 +-
drivers/dma/ti/omap-dma.c | 6 +++++-
4 files changed, 8 insertions(+), 4 deletions(-)
Thanks
--
~Vinod
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
reply other threads:[~2018-07-07 12:33 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=20180707121613.GY22377@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
all inboxes | Powered by JetHome®