public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: quic_zijuhu <quic_zijuhu@quicinc.com>
Cc: luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
	marcel@holtmann.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1 RESEND] Bluetooth: btusb: Correct timeout macro argument used to receive control message
Date: Mon, 22 Apr 2024 15:30:28 +0000	[thread overview]
Message-ID: <171379982891.28518.15878891828308361794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1713797830-24600-1-git-send-email-quic_zijuhu@quicinc.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon, 22 Apr 2024 22:57:10 +0800 you wrote:
> USB driver defines macro @USB_CTRL_SET_TIMEOUT for sending control message
> timeout and @USB_CTRL_GET_TIMEOUT for receiving, but usb_control_msg()
> uses wrong macro @USB_CTRL_SET_TIMEOUT as argument to receive control
> message, fixed by using @USB_CTRL_GET_TIMEOUT to receive message.
> 
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
> 
> [...]

Here is the summary with links:
  - [v1,RESEND] Bluetooth: btusb: Correct timeout macro argument used to receive control message
    https://git.kernel.org/bluetooth/bluetooth-next/c/927927f2471f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2024-04-22 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23  8:53 [PATCH] Bluetooth: btusb: Correct timeout macro argument used to receive control message Zijun Hu
2024-04-22 14:57 ` [PATCH v1 RESEND] " Zijun Hu
2024-04-22 15:30   ` patchwork-bot+bluetooth [this message]
2024-04-22 15:33   ` [v1,RESEND] " bluez.test.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=171379982891.28518.15878891828308361794.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=quic_zijuhu@quicinc.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