public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Yang Li via B4 Relay <devnull+yang.li.amlogic.com@kernel.org>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	catalin.marinas@arm.com, will@kernel.org,
	linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, yang.li@amlogic.com,
	krzysztof.kozlowski@linaro.org, ye.he@amlogic.com
Subject: Re: [PATCH v4 0/3] Add support for Amlogic HCI UART
Date: Fri, 09 Aug 2024 14:50:29 +0000	[thread overview]
Message-ID: <172321502977.3810378.15779692366071680309.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240809-btaml-v4-0-376b284405a7@amlogic.com>

Hello:

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

On Fri, 09 Aug 2024 13:42:23 +0800 you wrote:
> Add support for Amlogic HCI UART, including dt-binding,
> and Amlogic Bluetooth driver.
> 
> Signed-off-by: Yang Li <yang.li@amlogic.com>
> ---
> Changes in v4:
> - Modified the compatible list in the DT binding.
> - Reduced the boot delay from 350ms to 60ms.
> - Minor fixes.
> - Link to v3: https://lore.kernel.org/r/20240802-btaml-v3-0-d8110bf9963f@amlogic.com
> 
> [...]

Here is the summary with links:
  - [v4,1/3] dt-bindings: net: bluetooth: Add support for Amlogic Bluetooth
    https://git.kernel.org/bluetooth/bluetooth-next/c/8802f81065c3
  - [v4,2/3] Bluetooth: hci_uart: Add support for Amlogic HCI UART
    https://git.kernel.org/bluetooth/bluetooth-next/c/58803465ec1a
  - [v4,3/3] MAINTAINERS: Add an entry for Amlogic HCI UART (M: Yang Li)
    https://git.kernel.org/bluetooth/bluetooth-next/c/f173b220f9dc

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-08-09 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  5:42 [PATCH v4 0/3] Add support for Amlogic HCI UART Yang Li via B4 Relay
2024-08-09  5:42 ` [PATCH v4 1/3] dt-bindings: net: bluetooth: Add support for Amlogic Bluetooth Yang Li via B4 Relay
2024-08-09  6:40   ` Add support for Amlogic HCI UART bluez.test.bot
2024-08-09  5:42 ` [PATCH v4 2/3] Bluetooth: hci_uart: " Yang Li via B4 Relay
2024-08-09  5:42 ` [PATCH v4 3/3] MAINTAINERS: Add an entry for Amlogic HCI UART (M: Yang Li) Yang Li via B4 Relay
2024-08-09 14:50 ` 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=172321502977.3810378.15779692366071680309.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+yang.li.amlogic.com@kernel.org \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=will@kernel.org \
    --cc=yang.li@amlogic.com \
    --cc=ye.he@amlogic.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