Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Troy Mitchell" <troy.mitchell@linux.spacemit.com>
To: "Luiz Augusto von Dentz" <luiz.von.dentz@intel.com>
Cc: "Frédéric Mahé" <frederic.mahe@cirad.fr>,
	marcel@holtmann.org, luiz.dentz@gmail.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, dlan@kernel.org,
	anarsoul@gmail.com, alistair@alistair23.me, pjw@kernel.org,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	troy.mitchell@linux.spacemit.com,
	linux-bluetooth@vger.kernel.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Bluetooth for the RTL8852BS on BPI-F3
Date: Thu, 12 Nov 2026 01:45:52 +0000	[thread overview]
Message-ID: <DMSUPKS0VL8N.1RUUESQVU8FMF@linux.spacemit.com> (raw)
In-Reply-To: <179442601916.1604530.1705197925952408060.git-patchwork-notify@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 794 bytes --]

Hi Luiz,

On Wed, 11 Nov 2026 19:40:19 +0000, patchwork-bot+bluetooth@kernel.org wrote:
> This series was applied to bluetooth/bluetooth-next.git (master)
> by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

[...]
> Here is the summary with links:
>   - [v2,1/2] dt-bindings: net: bluetooth: realtek: Add RTL8852BS
>     https://git.kernel.org/bluetooth/bluetooth-next/c/c21f8cff7503
>   - [v2,2/2] riscv: dts: spacemit: enable Bluetooth on BPI-F3
>     https://git.kernel.org/bluetooth/bluetooth-next/c/df348a0d065c

SpacemiT DTS changes normally go through Yixun's tree to the SoC tree,
and Yixun hasn't acked this one yet. The binding patch is fine in
bluetooth-next.

Yixun, what do you think? Should Luiz drop the DTS patch and you pick it
up?

-- 
Troy Mitchell

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-11-12  1:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  9:45 [PATCH v2 0/2] Bluetooth for the RTL8852BS on BPI-F3 Frédéric Mahé
2026-11-11  9:45 ` [PATCH v2 1/2] dt-bindings: net: bluetooth: realtek: Add RTL8852BS Frédéric Mahé
2026-11-11  9:51   ` Troy Mitchell
2026-11-11  9:45 ` [PATCH v2 2/2] riscv: dts: spacemit: enable Bluetooth on BPI-F3 Frédéric Mahé
2026-11-11  9:52   ` Troy Mitchell
2026-11-11 19:40 ` [PATCH v2 0/2] Bluetooth for the RTL8852BS " patchwork-bot+bluetooth
2026-11-12  1:45   ` Troy Mitchell [this message]
2026-11-12  6:19     ` Yixun Lan
2026-11-12  8:56       ` Frédéric Mahé
2026-11-12  9:05         ` Troy Mitchell

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=DMSUPKS0VL8N.1RUUESQVU8FMF@linux.spacemit.com \
    --to=troy.mitchell@linux.spacemit.com \
    --cc=alex@ghiti.fr \
    --cc=alistair@alistair23.me \
    --cc=anarsoul@gmail.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlan@kernel.org \
    --cc=frederic.mahe@cirad.fr \
    --cc=krzk+dt@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=spacemit@lists.linux.dev \
    /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