[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250423165619.588e9d29@kernel.org>
Date: Wed, 23 Apr 2025 16:56:19 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jeff Layton <jlayton@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Simon Horman <horms@...nel.org>, Kuniyuki Iwashima
<kuniyu@...zon.com>, Qasim Ijaz <qasdev00@...il.com>, Nathan Chancellor
<nathan@...nel.org>, Andrew Lunn <andrew@...n.ch>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org, Thomas
Weißschuh <thomas.weissschuh@...utronix.de>
Subject: Re: [PATCH v4 0/7] ref_tracker: add ability to register a debugfs
file for a ref_tracker_dir
On Wed, 23 Apr 2025 19:48:29 -0400 Jeff Layton wrote:
> On Wed, 2025-04-23 at 16:44 -0700, Jakub Kicinski wrote:
> > On Fri, 18 Apr 2025 10:24:24 -0400 Jeff Layton wrote:
> > > This version should be pretty close to merge-ready. The only real
> > > difference is the use of NAME_MAX as the field width for on-stack
> > > sprintf buffers.
> >
> > Merge via which tree?
>
> Good Q. get_maintainer.pl says Andrew owns the ref_tracker code:
>
> $ ./scripts/get_maintainer.pl lib/ref_tracker.c
> Andrew Morton <akpm@...ux-foundation.org> (maintainer:LIBRARY CODE)
> linux-kernel@...r.kernel.org (open list:LIBRARY CODE)
> LIBRARY CODE status: Supported
>
> ...but I think he ends up owning anything without an explicit
> maintainer.
>
> Eric Dumazet wrote the ref_tracker originally though, and the new files
> are only added for networking stuff. If you wanted to pick it up, I
> doubt Andrew would mind.
My moderate excitement about the churn in the core networking core
aside :) - also no strong preferences on the tree. Looks like the
patches don't apply to net next:
Applying: net: register debugfs file for net_device refcnt tracker
Using index info to reconstruct a base tree...
M net/core/dev.c
Falling back to patching base and 3-way merge...
Auto-merging net/core/dev.c
so we could save a conflict by rebasing and routing them via the
networking trees?
Powered by blists - more mailing lists