netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Lukas Bulwahn <lbulwahn@redhat.com>
Cc: geert+renesas@glider.be, prabhakar.mahadev-lad.rj@bp.renesas.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	lukas.bulwahn@redhat.com
Subject: Re: [PATCH] MAINTAINERS: adjust file entry after renaming rzv2h-gbeth dtb
Date: Tue, 01 Jul 2025 01:40:10 +0000	[thread overview]
Message-ID: <175133401075.3632945.11017105407045410659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250627134453.51780-1-lukas.bulwahn@redhat.com>

Hello:

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

On Fri, 27 Jun 2025 15:44:53 +0200 you wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> 
> Commit d53320aeef18 ("dt-bindings: net: Rename
> renesas,r9a09g057-gbeth.yaml") renames the net devicetree binding
> renesas,r9a09g057-gbeth.yaml to renesas,rzv2h-gbeth.yaml, but misses to
> adjust the file entry in the RENESAS RZ/V2H(P) DWMAC GBETH GLUE LAYER
> DRIVER section in MAINTAINERS.
> 
> [...]

Here is the summary with links:
  - MAINTAINERS: adjust file entry after renaming rzv2h-gbeth dtb
    https://git.kernel.org/netdev/net/c/3b2c45cb1b50

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-01  1:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 13:44 [PATCH] MAINTAINERS: adjust file entry after renaming rzv2h-gbeth dtb Lukas Bulwahn
2025-06-27 14:41 ` Geert Uytterhoeven
2025-06-27 20:06 ` Simon Horman
2025-06-30 13:24 ` Lad, Prabhakar
2025-07-01  1:40 ` 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=175133401075.3632945.11017105407045410659.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=geert+renesas@glider.be \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=lbulwahn@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=lukas.bulwahn@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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 NNTP newsgroup(s).