From: Vinod <vkoul@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: soundwire fixes for v4.19
Date: Wed, 12 Sep 2018 15:27:42 +0530 [thread overview]
Message-ID: <20180912095622.GJ2766@vkoul-mobl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
Hi Greg,
Please pull to receive soundwire fixes for 4.19, these include stream
state and lock fix on release.
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-4.19-fixes
for you to fetch changes up to 8d6ccf5cebbc7ed1dee9986e36853a78dfb64084:
soundwire: Fix acquiring bus lock twice during master release (2018-08-27 09:49:48 +0530)
----------------------------------------------------------------
soundwire fixes for 4.19
- fixes in bus for
- bus lock on master release
- incorrect exit after stream configuration
- duplicate stream state assignment
----------------------------------------------------------------
Sanyog Kale (1):
soundwire: Fix acquiring bus lock twice during master release
Shreyas NC (2):
soundwire: Fix duplicate stream state assignment
soundwire: Fix incorrect exit after configuring stream
drivers/soundwire/stream.c | 23 +++++++++++++++++------
1 file changed, 17 insertions(+), 6 deletions(-)
--
~Vinod
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2018-09-12 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 9:57 Vinod [this message]
2018-09-18 9:13 ` soundwire fixes for v4.19 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=20180912095622.GJ2766@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
/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).