From: patchwork-bot+netdevbpf@kernel.org
To: Frank Li <Frank.Li@nxp.com>
Cc: robh@kernel.org, conor+dt@kernel.org, davem@davemloft.net,
devicetree@vger.kernel.org, edumazet@google.com,
imx@lists.linux.dev, krzk+dt@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, madalin.bucur@nxp.com,
netdev@vger.kernel.org, pabeni@redhat.com,
sean.anderson@seco.com
Subject: Re: [PATCH v4 1/2] dt-bindings: net: fsl,fman: allow dma-coherent property
Date: Tue, 09 Jul 2024 19:02:01 +0000 [thread overview]
Message-ID: <172055172184.32169.14387199835490742511.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240708180949.1898495-1-Frank.Li@nxp.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 8 Jul 2024 14:09:48 -0400 you wrote:
> Add dma-coherent property to fix below warning.
> arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dtb: fman@1a00000: 'dma-coherent', 'ptimer-handle' do not match any of the regexes: '^ethernet@[a-f0-9]+$', '^mdio@[a-f0-9]+$', '^muram@[a-f0-9]+$', '^phc@[a-f0-9]+$', '^port@[a-f0-9]+$', 'pinctrl-[0-9]+'
> from schema $id: http://devicetree.org/schemas/net/fsl,fman.yaml#
>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
>
> [...]
Here is the summary with links:
- [v4,1/2] dt-bindings: net: fsl,fman: allow dma-coherent property
https://git.kernel.org/netdev/net-next/c/dd84d831ef27
- [v4,2/2] dt-bindings: net: fsl,fman: add ptimer-handle property
https://git.kernel.org/netdev/net-next/c/5618ced01979
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-09 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 18:09 [PATCH v4 1/2] dt-bindings: net: fsl,fman: allow dma-coherent property Frank Li
2024-07-08 18:09 ` [PATCH v4 2/2] dt-bindings: net: fsl,fman: add ptimer-handle property Frank Li
2024-07-09 19:02 ` patchwork-bot+netdevbpf [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=172055172184.32169.14387199835490742511.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sean.anderson@seco.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