From: patchwork-bot+bluetooth@kernel.org
To: Xianting Tian <xianting.tian@linux.alibaba.com>
Cc: arei.gonglei@huawei.com, mst@redhat.com, jasowang@redhat.com,
xuanzhuo@linux.alibaba.com, herbert@gondor.apana.org.au,
davem@davemloft.net, amit@kernel.org, arnd@arndb.de,
gregkh@linuxfoundation.org, marcel@holtmann.org,
johan.hedberg@gmail.com, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] fixup potential cpu stall
Date: Thu, 06 Jul 2023 20:10:10 +0000 [thread overview]
Message-ID: <168867421006.27620.2867140526566551543.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230609131817.712867-1-xianting.tian@linux.alibaba.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Michael S. Tsirkin <mst@redhat.com>:
On Fri, 9 Jun 2023 21:18:14 +0800 you wrote:
> Cpu stall issue may happen if device is configured with multi queues
> and large queue depth, so fix it.
>
> Xianting Tian (3):
> virtio-crypto: fixup potential cpu stall when free unused bufs
> virtio_console: fixup potential cpu stall when free unused bufs
> virtio_bt: fixup potential cpu stall when free unused bufs
>
> [...]
Here is the summary with links:
- [1/3] virtio-crypto: fixup potential cpu stall when free unused bufs
https://git.kernel.org/bluetooth/bluetooth-next/c/7a5103b81a96
- [2/3] virtio_console: fixup potential cpu stall when free unused bufs
https://git.kernel.org/bluetooth/bluetooth-next/c/56b5e65efe00
- [3/3] virtio_bt: fixup potential cpu stall when free unused bufs
https://git.kernel.org/bluetooth/bluetooth-next/c/3845308fc8b0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-07-06 20:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 13:18 [PATCH 0/3] fixup potential cpu stall Xianting Tian
2023-06-09 13:18 ` [PATCH 1/3] virtio-crypto: fixup potential cpu stall when free unused bufs Xianting Tian
2023-06-09 13:39 ` Greg KH
2023-06-09 13:39 ` Greg KH
2023-06-09 13:41 ` Greg KH
2023-06-09 13:41 ` Greg KH
2023-06-09 13:49 ` Xianting Tian
2023-06-09 14:05 ` Greg KH
2023-06-09 14:05 ` Greg KH
2023-06-09 14:25 ` Xianting Tian
2023-06-09 16:02 ` Michael S. Tsirkin
2023-06-09 16:02 ` Michael S. Tsirkin
2023-06-09 13:57 ` fixup potential cpu stall bluez.test.bot
2023-06-09 15:57 ` [PATCH 1/3] virtio-crypto: fixup potential cpu stall when free unused bufs Michael S. Tsirkin
2023-06-09 15:57 ` Michael S. Tsirkin
2023-06-10 3:20 ` Xianting Tian
2023-06-10 6:51 ` Greg KH
2023-06-10 6:51 ` Greg KH
2023-06-09 15:58 ` Michael S. Tsirkin
2023-06-09 15:58 ` Michael S. Tsirkin
2023-06-09 13:18 ` [PATCH 2/3] virtio_console: " Xianting Tian
2023-06-09 16:05 ` Michael S. Tsirkin
2023-06-09 16:05 ` Michael S. Tsirkin
2023-06-10 3:19 ` Xianting Tian
2023-06-09 13:18 ` [PATCH 3/3] virtio_bt: " Xianting Tian
2023-06-22 11:59 ` [PATCH 0/3] fixup potential cpu stall Michael S. Tsirkin
2023-06-22 11:59 ` Michael S. Tsirkin
2023-06-23 0:58 ` Xianting Tian
2023-07-06 20:10 ` patchwork-bot+bluetooth [this message]
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=168867421006.27620.2867140526566551543.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amit@kernel.org \
--cc=arei.gonglei@huawei.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xianting.tian@linux.alibaba.com \
--cc=xuanzhuo@linux.alibaba.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 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.