public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Golle <daniel@makrotopia.org>
Cc: nbd@nbd.name, frank-w@public-files.de, ericwouds@gmail.com,
	eladwf@gmail.com, bc-bocun.chen@mediatek.com,
	skylake.huang@mediatek.com, sean.wang@mediatek.com,
	lorenzo@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net-next v5 0/3] net: ethernet: mtk_eth_soc: improve device tree handling
Date: Tue, 08 Jul 2025 02:10:42 +0000	[thread overview]
Message-ID: <175194064274.3543842.9948316724629188569.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1751461762.git.daniel@makrotopia.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 2 Jul 2025 14:14:20 +0100 you wrote:
> This series further improves the mtk_eth_soc driver in preparation to
> complete upstream support for the MediaTek MT7988 SoC family.
> 
> Frank Wunderlich's previous attempt to have the ethernet node included
> in mt7988a.dtsi and cover support for MT7988 in the device tree bindings
> was criticized for the way mtk_eth_soc references SRAM in device tree[1].
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/3] net: ethernet: mtk_eth_soc: improve support for named interrupts
    https://git.kernel.org/netdev/net-next/c/e81d36d48880
  - [net-next,v5,2/3] net: ethernet: mtk_eth_soc: fix kernel-doc comment
    https://git.kernel.org/netdev/net-next/c/d717d32f517f
  - [net-next,v5,3/3] net: ethernet: mtk_eth_soc: use generic allocator for SRAM
    https://git.kernel.org/netdev/net-next/c/04c7aaccdcf6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




      parent reply	other threads:[~2025-07-08  2:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 13:14 [PATCH net-next v5 0/3] net: ethernet: mtk_eth_soc: improve device tree handling Daniel Golle
2025-07-02 13:14 ` [PATCH net-next v5 1/3] net: ethernet: mtk_eth_soc: improve support for named interrupts Daniel Golle
2025-07-02 13:14 ` [PATCH net-next v5 2/3] net: ethernet: mtk_eth_soc: fix kernel-doc comment Daniel Golle
2025-07-02 13:14 ` [PATCH net-next v5 3/3] net: ethernet: mtk_eth_soc: use generic allocator for SRAM Daniel Golle
2025-07-08  2:10 ` 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=175194064274.3543842.9948316724629188569.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=bc-bocun.chen@mediatek.com \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eladwf@gmail.com \
    --cc=ericwouds@gmail.com \
    --cc=frank-w@public-files.de \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=lorenzo@kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=nbd@nbd.name \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sean.wang@mediatek.com \
    --cc=skylake.huang@mediatek.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