mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL]: SoundWire subsystem fixes for v6.1
Date: Thu, 10 Nov 2022 15:14:03 +0530	[thread overview]
Message-ID: <Y2zH4zDyx5kWaUvz@matsya> (raw)

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

Hey Linus,

Please pull to receive three fixes in drivers for this cycle.

The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:

  Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-6.1-fixes

for you to fetch changes up to 49a467310dc4fae591a3547860ee04d8730780f4:

  soundwire: qcom: check for outanding writes before doing a read (2022-10-28 17:00:38 +0530)

----------------------------------------------------------------
soundwire fixes for v6.1

This contains two qcom driver fixes for broadcast completion reinit and
check for outanding writes. Lone Intel driver fix for clock stop timeout

----------------------------------------------------------------
Sjoerd Simons (1):
      soundwire: intel: Initialize clock stop timeout

Srinivas Kandagatla (2):
      soundwire: qcom: reinit broadcast completion
      soundwire: qcom: check for outanding writes before doing a read

 drivers/soundwire/intel.c | 1 +
 drivers/soundwire/qcom.c  | 9 +++++++++
 2 files changed, 10 insertions(+)

Thanks
-- 
~Vinod

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

             reply	other threads:[~2022-11-10  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  9:44 Vinod Koul [this message]
2022-11-10 17:03 ` 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=Y2zH4zDyx5kWaUvz@matsya \
    --to=vkoul@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®