From: Vinod Koul <vkoul@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: alsa-devel@alsa-project.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: [GIT PULL]: soundwire fixes for v5.2-rc4
Date: Fri, 7 Jun 2019 15:26:33 +0530 [thread overview]
Message-ID: <20190607095633.GD9160@vkoul-mobl.Dlink> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1227 bytes --]
Hey Greg,
Please consider pull to receive fixes for soundwire for 5.2. We have 3
fixes done by Srini and all are in linux-next
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-5.2-rc4
for you to fetch changes up to 39194128701bf2af9bbc420ffe6e3cb5d2c16061:
soundwire: intel: set dai min and max channels correctly (2019-06-06 22:48:41 +0530)
----------------------------------------------------------------
soundwire fixes for v5.2-rc4
Srinivas Kandagatla fixed by bunch of issues, two in core for locking
and out of bound access and one in intel driver copy-paste
----------------------------------------------------------------
Srinivas Kandagatla (3):
soundwire: stream: fix out of boundary access on port properties
soundwire: stream: fix bad unlock balance
soundwire: intel: set dai min and max channels correctly
drivers/soundwire/intel.c | 4 ++--
drivers/soundwire/stream.c | 7 +++----
2 files changed, 5 insertions(+), 6 deletions(-)
Thanks
--
~Vinod
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2019-06-07 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 9:56 Vinod Koul [this message]
2019-06-10 16:08 ` [GIT PULL]: soundwire fixes for v5.2-rc4 Greg KH
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=20190607095633.GD9160@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=gregkh@linuxfoundation.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=srinivas.kandagatla@linaro.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