All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dma <dmaengine@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT,PULL] : dmaengine fixes for 4.16-rc7
Date: Sun, 25 Mar 2018 14:37:06 +0530	[thread overview]
Message-ID: <20180325090705.GE15443@localhost> (raw)

Hello Linus,

We have a small buffer over flow fix for stm32 driver, please pull to
receive this.

Also note that somehow I was not able to push it at regular git.infradead.org
server I use, so updated on kernel.org tree


The following changes since commit 0c8efd610b58cb23cefdfa12015799079aef94ae:

  Linux 4.16-rc5 (2018-03-11 17:25:09 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/slave-dma.git tags/dmaengine-fix-4.16-rc7

for you to fetch changes up to 3e4543bf20531d1cdb8672d25b3f2ff6d3d07627:

  dmaengine: stm32-dmamux: fix a potential buffer overflow (2018-03-22 10:51:35 +0530)

----------------------------------------------------------------
dmaengine fixes for v4.16-rc7

One small fix for stm32-dmamux fixing buffer overflow.

----------------------------------------------------------------
Pierre-Yves MORDRET (1):
      dmaengine: stm32-dmamux: fix a potential buffer overflow

 drivers/dma/stm32-dmamux.c | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

Thanks

WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dma <dmaengine@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL]: dmaengine fixes for 4.16-rc7
Date: Sun, 25 Mar 2018 14:37:06 +0530	[thread overview]
Message-ID: <20180325090705.GE15443@localhost> (raw)

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

Hello Linus,

We have a small buffer over flow fix for stm32 driver, please pull to
receive this.

Also note that somehow I was not able to push it at regular git.infradead.org
server I use, so updated on kernel.org tree


The following changes since commit 0c8efd610b58cb23cefdfa12015799079aef94ae:

  Linux 4.16-rc5 (2018-03-11 17:25:09 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/slave-dma.git tags/dmaengine-fix-4.16-rc7

for you to fetch changes up to 3e4543bf20531d1cdb8672d25b3f2ff6d3d07627:

  dmaengine: stm32-dmamux: fix a potential buffer overflow (2018-03-22 10:51:35 +0530)

----------------------------------------------------------------
dmaengine fixes for v4.16-rc7

One small fix for stm32-dmamux fixing buffer overflow.

----------------------------------------------------------------
Pierre-Yves MORDRET (1):
      dmaengine: stm32-dmamux: fix a potential buffer overflow

 drivers/dma/stm32-dmamux.c | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

Thanks
-- 
~Vinod

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

             reply	other threads:[~2018-03-25  9:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-25  9:07 Vinod Koul [this message]
2018-03-25  9:07 ` [GIT PULL]: dmaengine fixes for 4.16-rc7 Vinod Koul

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=20180325090705.GE15443@localhost \
    --to=vinod.koul@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.