From: Rob Herring <robh@kernel.org>
To: patchwork-bot+bluetooth@kernel.org
Cc: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>,
marcel@holtmann.org, luiz.dentz@gmail.com, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
amitkumar.karwar@nxp.com, sherry.sun@nxp.com,
manjeet.gupta@nxp.com
Subject: Re: [PATCH v3 1/2] dt-bindings: net: bluetooth: nxp: Add support for host-wakeup
Date: Tue, 15 Apr 2025 18:27:04 -0500 [thread overview]
Message-ID: <20250415232704.GA956317-robh@kernel.org> (raw)
In-Reply-To: <174474844000.2765712.3519619421796978194.git-patchwork-notify@kernel.org>
On Tue, Apr 15, 2025 at 08:20:40PM +0000, patchwork-bot+bluetooth@kernel.org wrote:
> Hello:
>
> This series was applied to bluetooth/bluetooth-next.git (master)
> by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
>
> On Mon, 14 Apr 2025 23:29:51 +0530 you wrote:
> > Add support for host wakeup on interrupt.
> >
> > Signed-off-by: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
> > ---
> > v2: Use interrupt instead of host-wakeup-gpios. (Rob Herring)
> > v3: Fix errors in dt_binding_check. (Neeraj Kale)
> >
> > [...]
>
> Here is the summary with links:
> - [v3,1/2] dt-bindings: net: bluetooth: nxp: Add support for host-wakeup
> https://git.kernel.org/bluetooth/bluetooth-next/c/f68f62f57917
I happen to have no more comments in this case, but please let DT
maintainers have a chance to ack/review bindings.
Rob
prev parent reply other threads:[~2025-04-15 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 17:59 [PATCH v3 1/2] dt-bindings: net: bluetooth: nxp: Add support for host-wakeup Neeraj Sanjay Kale
2025-04-14 17:59 ` [PATCH v3 2/2] Bluetooth: btnxpuart: Implement host-wakeup feature Neeraj Sanjay Kale
2025-04-15 23:32 ` kernel test robot
2025-04-14 18:39 ` [v3,1/2] dt-bindings: net: bluetooth: nxp: Add support for host-wakeup bluez.test.bot
2025-04-15 20:20 ` [PATCH v3 1/2] " patchwork-bot+bluetooth
2025-04-15 23:27 ` Rob Herring [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=20250415232704.GA956317-robh@kernel.org \
--to=robh@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=manjeet.gupta@nxp.com \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=patchwork-bot+bluetooth@kernel.org \
--cc=sherry.sun@nxp.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.