Netdev List
 help / color / mirror / Atom feed
From: Kory Maincent <kory.maincent@bootlin.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Donald Hunter <donald.hunter@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net 1/3] MAINTAINERS: Add myself as maintainer for socket timestamping and expand file list
Date: Thu, 30 Jan 2025 10:18:11 +0100	[thread overview]
Message-ID: <20250130101811.5459c3f8@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <20250129163916.46b2ea5c@kernel.org>

On Wed, 29 Jan 2025 16:39:16 -0800
Jakub Kicinski <kuba@kernel.org> wrote:

> On Tue, 28 Jan 2025 16:35:46 +0100 Kory Maincent wrote:
> > Add myself as maintainer for socket timestamping. I have contributed
> > modifications to the timestamping core to support selection between
> > multiple PTP instances within a network topology.
> > 
> > Expand the file list to include timestamping ethtool support.  
> 
> Hi Kory, is there more context you could provide for this change?
> 
> For core pieces of the stack, with a long history, we tend to
> designate as maintainer folks who review the changes, not just
> write code. According to our development stats that doesn't
> describe you, just yet:
> 
> Top reviewer score:
> 
> 6.12: Negative # 5 ( +6) [ 50] Kory Maincent (Dent Project)
> 6.13: Negative #11 (***) [ 29] Kory Maincent (Dent Project)

Yes indeed, I am not really confident reviewing code part that I don't know
well. My thought that I did not have lots on review in the PTP patch series I
just managed to get merged. So I would try to change that.
Moreover I have changed a bit the management of time stamping configuration so
if there is changes or fixes I could be helpful.
Indeed adding myself as maintainer is a bit overestimated, maybe I could be set
as a reviewer to be in the CC of the patches.

> https://lore.kernel.org/20250121200710.19126f7d@kernel.org
> https://lore.kernel.org/20241119191608.514ea226@kernel.org
> https://lore.kernel.org/20240922190125.24697d06@kernel.org
> 
> That said, I do feel like we're lacking maintainers for sections 
> of the ethtool code. Maybe we could start with adding and entry 
> for you for just:
> 
> > +F:	net/ethtool/tsconfig.c
> > +F:	net/ethtool/tsinfo.c  
> 
> Does that sound fair?

Yes it does. Whether setting me as reviewer for the SOCKET TIMESTAMPING subpart
or adding me as maintainer of these two files it is ok for me. What do you
prefer?

I will try to review more ethtool code now that I began to understand how it
works thanks to my PoE and PTP work. 

Regards,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

  reply	other threads:[~2025-01-30  9:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28 15:35 [PATCH net 0/3] net: ethtool: timestamping: Fix small issues in the new uAPI Kory Maincent
2025-01-28 15:35 ` [PATCH net 1/3] MAINTAINERS: Add myself as maintainer for socket timestamping and expand file list Kory Maincent
2025-01-30  0:39   ` Jakub Kicinski
2025-01-30  9:18     ` Kory Maincent [this message]
2025-01-30 16:31       ` Jakub Kicinski
2025-01-30 16:56         ` Kory Maincent
2025-01-28 15:35 ` [PATCH net 2/3] net: ethtool: tsconfig: Fix ts filters and types enums size check Kory Maincent
2025-01-30  0:45   ` Jakub Kicinski
2025-01-30  9:24     ` Kory Maincent
2025-01-30 16:42       ` Jakub Kicinski
2025-01-28 15:35 ` [PATCH net 3/3] net: ethtool: tsconfig: Fix netlink type of hwtstamp flags Kory Maincent
2025-01-30  0:49   ` Jakub Kicinski
2025-01-30  9:27     ` Kory Maincent
2025-01-30 16:43       ` Jakub Kicinski

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=20250130101811.5459c3f8@kmaincent-XPS-13-7390 \
    --to=kory.maincent@bootlin.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=willemdebruijn.kernel@gmail.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