All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: WangYuli <wangyuli@uniontech.com>
Cc: Larry.Finger@lwfinger.net, marcel@holtmann.org,
	luiz.dentz@gmail.com, gustavo@padovan.org,
	johan.hedberg@gmail.com, guanwentao@uniontech.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [RESEND. PATCH v2] Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x0bda:0x4853
Date: Thu, 11 Apr 2024 14:39:43 +0000	[thread overview]
Message-ID: <171284638325.18150.6436513987613825530.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <883A1BECA61AB8B7+20240329023440.191799-1-wangyuli@uniontech.com>

Hello:

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

On Fri, 29 Mar 2024 10:34:39 +0800 you wrote:
> Add the support ID(0x0bda, 0x4853) to usb_device_id table for
> Realtek RTL8852BE.
> 
> Without this change the device utilizes an obsolete version of
> the firmware that is encoded in it rather than the updated Realtek
> firmware and config files from the firmware directory. The latter
> files implement many new features.
> 
> [...]

Here is the summary with links:
  - [RESEND.,v2] Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x0bda:0x4853
    https://git.kernel.org/bluetooth/bluetooth-next/c/cf396a443d37

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



      parent reply	other threads:[~2024-04-11 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29  2:34 [RESEND. PATCH v2] Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x0bda:0x4853 WangYuli
2024-03-29  3:32 ` [RESEND.,v2] " bluez.test.bot
2024-04-11 14:39 ` 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=171284638325.18150.6436513987613825530.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=guanwentao@uniontech.com \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=stable@vger.kernel.org \
    --cc=wangyuli@uniontech.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.