From: patchwork-bot+bluetooth@kernel.org
To: Hans de Goede <johannes.goede@oss.qualcomm.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
iabdelka@qti.qualcomm.com, linux-arm-msm@vger.kernel.org,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: hci_core: Return -ENOMEM when the sent_cmd clone fails
Date: Tue, 18 Aug 2026 18:37:34 +0000 [thread overview]
Message-ID: <178707825486.2194892.5994990121854718172.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260817205017.56524-1-johannes.goede@oss.qualcomm.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 17 Aug 2026 22:50:16 +0200 you wrote:
> From: Ibrahim Abdelkader <iabdelka@qti.qualcomm.com>
>
> hci_send_cmd_sync() returns -EINVAL when skb_clone() fails for sent_cmd,
> which describes an invalid argument rather than an allocation failure.
>
> Return -ENOMEM instead. The only caller, hci_cmd_work(), tests the result
> for zero, so there is no functional change.
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: hci_core: Return -ENOMEM when the sent_cmd clone fails
https://git.kernel.org/bluetooth/bluetooth-next/c/57f558cf1a3d
- [2/2] Bluetooth: hci_core: Handle skb_clone() failure in hci_send_cmd_sync()
(no matching commit)
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:[~2026-08-18 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 20:50 [PATCH 1/2] Bluetooth: hci_core: Return -ENOMEM when the sent_cmd clone fails Hans de Goede
2026-08-17 20:50 ` [PATCH 2/2] Bluetooth: hci_core: Handle skb_clone() failure in hci_send_cmd_sync() Hans de Goede
2026-08-18 18:01 ` Luiz Augusto von Dentz
2026-08-17 21:46 ` [1/2] Bluetooth: hci_core: Return -ENOMEM when the sent_cmd clone fails bluez.test.bot
2026-08-18 18:37 ` 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=178707825486.2194892.5994990121854718172.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=iabdelka@qti.qualcomm.com \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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.