From: Yixun Lan <dlan@kernel.org>
To: Troy Mitchell <troy.mitchell@linux.spacemit.com>
Cc: "Luiz Augusto von Dentz" <luiz.von.dentz@intel.com>,
"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, anarsoul@gmail.com,
alistair@alistair23.me, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr,
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 06:19:51 +0000 [thread overview]
Message-ID: <20261112061951-GKA62271@kernel.org> (raw)
In-Reply-To: <DMSUPKS0VL8N.1RUUESQVU8FMF@linux.spacemit.com>
Hi Luiz, Troy,
On 01:45 Thu 12 Nov , Troy Mitchell wrote:
> 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.
>
This do happen sometimes.. I agree with the split, or another solution -
I could also take patch 1/2 with bluethooth maintainer's Ack, either way
is fine by me
> Yixun, what do you think? Should Luiz drop the DTS patch and you pick it
> up?
>
Ideally, the DT part patch [2/2] should go through SpacemiT's SoC tree,
which would avoid potential unnecessary conflicts.. besides, the DT maintainer
did complain about this thing before and request dts go through soc tree, see
https://lore.kernel.org/all/20260918-belligerent-succinct-kraken-7fa592@quoll/
--
Yixun Lan (dlan)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-11-12 6:20 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
2026-11-12 6:19 ` Yixun Lan [this message]
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=20261112061951-GKA62271@kernel.org \
--to=dlan@kernel.org \
--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=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 \
--cc=troy.mitchell@linux.spacemit.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