netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: davem@davemloft.net, Andrew Lunn <andrew@lunn.ch>,
	Jakub Kicinski <kuba@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	thomas.petazzoni@bootlin.com,
	Russell King <linux@armlinux.org.uk>,
	Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net-next] MAINTAINERS: Add dedicated entries for phy_link_topology
Date: Fri, 21 Mar 2025 18:37:37 +0100	[thread overview]
Message-ID: <20250321183737.594b665c@fedora.home> (raw)
In-Reply-To: <08d9509a-3291-4856-8129-1e440df10b29@redhat.com>

On Fri, 21 Mar 2025 17:05:08 +0100
Paolo Abeni <pabeni@redhat.com> wrote:

> On 3/13/25 4:30 PM, Maxime Chevallier wrote:
> > The infrastructure to handle multi-phy devices is fairly standalone.
> > Add myself as maintainer for that part as well as the netlink uAPI
> > that exposes it.
> > 
> > Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>  
> 
> I'd like to have Jakub on-board here. He should be back soonish, so
> let's keep this patch around a little more
> 
> Note that MAINTAINER changes go via the 'net' tree.

Ah sorry about that, I missed this bit of process. I'll resubmit on
'net' if Jakub acks this :)

Maxime


  reply	other threads:[~2025-03-21 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 15:30 [PATCH net-next] MAINTAINERS: Add dedicated entries for phy_link_topology Maxime Chevallier
2025-03-17 21:17 ` Andrew Lunn
2025-03-21 16:05 ` Paolo Abeni
2025-03-21 17:37   ` Maxime Chevallier [this message]
2025-03-24 12:15 ` Jakub Kicinski
2025-03-27 10:43 ` Maxime Chevallier

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=20250321183737.594b665c@fedora.home \
    --to=maxime.chevallier@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=thomas.petazzoni@bootlin.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).