From: Nils Helmig <nils.helmig@web.de>
To: bluez.test.bot@gmail.com
Cc: linux-bluetooth@vger.kernel.org, nils.helmig@web.de
Subject: RE: [v2] Bluetooth: btusb: Add TP-Link UB600 for Realtek 8761BUV
Date: Tue, 26 May 2026 21:03:23 +0200 [thread overview]
Message-ID: <20260526190323.5930-1-nils.helmig@web.de> (raw)
In-Reply-To: <69ed185e.050a0220.107d78.67fa@mx.google.com>
From: nils.helmig@web.de
I saw that the merge request https://github.com/bluez/bluetooth-next/pull/127 is closed. Any news on this patch? Is there something I should do?
Regards,
Nils Helmig
next prev parent reply other threads:[~2026-05-26 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 18:56 [PATCH v2] Bluetooth: btusb: Add TP-Link UB600 for Realtek 8761BUV Nils Helmig
2026-04-25 19:39 ` [v2] " bluez.test.bot
2026-05-26 19:03 ` Nils Helmig [this message]
2026-05-29 13:38 ` Nils Helmig
2026-05-29 18:25 ` Paul Menzel
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=20260526190323.5930-1-nils.helmig@web.de \
--to=nils.helmig@web.de \
--cc=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox