From: patchwork-bot+netdevbpf@kernel.org
To: Peng Fan (OSS) <peng.fan@oss.nxp.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, xiaoning.wang@nxp.com,
linux-imx@nxp.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, peng.fan@nxp.com
Subject: Re: [PATCH] dt-bindings: net: nxp,dwmac-imx: allow nvmem cells property
Date: Wed, 17 Apr 2024 00:20:32 +0000 [thread overview]
Message-ID: <171331323265.29224.3287765599809023599.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240415103621.1644735-1-peng.fan@oss.nxp.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 15 Apr 2024 18:36:21 +0800 you wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Allow nvmem-cells and nvmem-cell-names to get mac_address from onchip
> fuse.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
>
> [...]
Here is the summary with links:
- dt-bindings: net: nxp,dwmac-imx: allow nvmem cells property
https://git.kernel.org/netdev/net-next/c/427f6acbc881
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-04-17 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 10:36 [PATCH] dt-bindings: net: nxp,dwmac-imx: allow nvmem cells property Peng Fan (OSS)
2024-04-15 14:36 ` Frank Li
2024-04-15 15:47 ` Conor Dooley
2024-04-16 13:52 ` Peng Fan
2024-04-16 14:35 ` Conor Dooley
2024-04-17 0:20 ` 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=171331323265.29224.3287765599809023599.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=xiaoning.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).