All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka@chromium.org>
To: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org,
	Rocky Liao <rjliao@codeaurora.org>,
	Zijun Hu <zijuhu@codeaurora.org>,
	linux-kernel@vger.kernel.org,
	Balakrishna Godavarthi <bgodavar@codeaurora.org>,
	Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
	Claire Chang <tientzu@chromium.org>,
	Matthias Kaehlcke <mka@chromium.org>
Subject: [PATCH 0/3]
Date: Fri,  5 Jun 2020 11:46:08 -0700	[thread overview]
Message-ID: <20200605184611.252218-1-mka@chromium.org> (raw)

This series includes a fix for a possible race in qca_suspend() and
some minor refactoring of the same function.


Matthias Kaehlcke (3):
  Bluetooth: hci_qca: Only remove TX clock vote after TX is completed
  Bluetooth: hci_qca: Skip serdev wait when no transfer is pending
  Bluetooth: hci_qca: Refactor error handling in qca_suspend()

 drivers/bluetooth/hci_qca.c | 22 ++++++++++++----------
 1 file changed, 12 insertions(+), 10 deletions(-)

-- 
2.27.0.278.ge193c7cf3a9-goog


             reply	other threads:[~2020-06-05 18:46 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 18:46 Matthias Kaehlcke [this message]
2020-06-05 18:46 ` [PATCH 1/3] Bluetooth: hci_qca: Only remove TX clock vote after TX is completed Matthias Kaehlcke
2020-06-05 20:44   ` Abhishek Pandit-Subedi
2020-06-06 12:53   ` bgodavar
2020-06-06 15:26     ` Matthias Kaehlcke
2020-06-08  8:11   ` Marcel Holtmann
2020-06-05 18:46 ` [PATCH 2/3] Bluetooth: hci_qca: Skip serdev wait when no transfer is pending Matthias Kaehlcke
2020-06-05 20:45   ` Abhishek Pandit-Subedi
2020-06-06 12:57   ` bgodavar
2020-06-06 14:42     ` Matthias Kaehlcke
2020-06-08  8:13   ` Marcel Holtmann
2020-06-05 18:46 ` [PATCH 3/3] Bluetooth: hci_qca: Refactor error handling in qca_suspend() Matthias Kaehlcke
2020-06-05 20:46   ` Abhishek Pandit-Subedi
2020-06-08  8:14   ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2023-12-19  8:51 [PATCH 0/3] Mitul Golani
2023-10-31  3:36 Zhu Ning
2022-01-03  9:21 Antoniu Miclaus
2020-04-27  8:21 Gareth Williams
2020-04-27  8:21 ` Gareth Williams
2020-04-27 13:21 ` Gareth Williams
2020-04-27 13:21   ` Gareth Williams
2020-01-09 17:11 Patrick Delaunay
2015-07-01 13:41 Ben Catterall
2015-02-27 21:25 Melike Yurtoglu
2015-02-27 20:42 Melike Yurtoglu
2015-02-27 19:51 Melike Yurtoglu
2013-09-21 13:05 Fan Rong
2013-09-21 13:05 ` Fan Rong
2013-06-06 13:53 Jani Nikula
2013-06-06 13:53 ` Jani Nikula
2013-06-06 13:59 ` Jani Nikula
2013-06-06 13:59   ` Jani Nikula
2013-06-13  8:22   ` Daniel Vetter
2013-06-13  8:22     ` Daniel Vetter
2013-06-14 16:23     ` Greg Kroah-Hartman
2013-06-06 14:33 ` Daniel Vetter
2013-03-01 17:34 tom.zanussi
2012-03-03 10:59 Xiaofeng Yan
2012-03-04 12:24 ` Richard Purdie
2009-04-16  9:37 dmitry.krivoschekov
2009-04-17  8:23 ` David Miller
2005-12-12  0:41 Petr Baudis

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=20200605184611.252218-1-mka@chromium.org \
    --to=mka@chromium.org \
    --cc=abhishekpandit@chromium.org \
    --cc=bgodavar@codeaurora.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=rjliao@codeaurora.org \
    --cc=tientzu@chromium.org \
    --cc=zijuhu@codeaurora.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.