All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <jlayton@kernel.org>
Cc: <akpm@linux-foundation.org>, <andrew@lunn.ch>,
	<davem@davemloft.net>, <edumazet@google.com>, <horms@kernel.org>,
	<kuba@kernel.org>, <linux-kernel@vger.kernel.org>,
	<netdev@vger.kernel.org>, <pabeni@redhat.com>,
	Kuniyuki Iwashima <kuniyu@amazon.com>
Subject: Re: [PATCH v2 1/2] ref_tracker: add a top level debugfs directory for ref_tracker
Date: Wed, 9 Apr 2025 21:27:27 -0700	[thread overview]
Message-ID: <20250410042729.28604-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250408-netns-debugfs-v2-1-ca267f51461e@kernel.org>

From: Jeff Layton <jlayton@kernel.org>
Date: Tue, 08 Apr 2025 09:36:37 -0400
> Add a new "ref_tracker" directory in debugfs. Each individual refcount
> tracker can add a directory or files under there to display info about
> currently-held references.
> 
> Signed-off-by: Jeff Layton <jlayton@kernel.org>

Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>


  reply	other threads:[~2025-04-10  4:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 13:36 [PATCH v2 0/2] net: add debugfs files for showing netns refcount tracking info Jeff Layton
2025-04-08 13:36 ` [PATCH v2 1/2] ref_tracker: add a top level debugfs directory for ref_tracker Jeff Layton
2025-04-10  4:27   ` Kuniyuki Iwashima [this message]
2025-04-10 12:05   ` Andrew Lunn
2025-04-08 13:36 ` [PATCH v2 2/2] net: add debugfs files for showing netns refcount tracking info Jeff Layton
2025-04-10  4:24   ` Kuniyuki Iwashima
2025-04-10 12:36   ` Andrew Lunn
2025-04-10 13:08     ` Jeff Layton
2025-04-10 13:23       ` Jeff Layton
2025-04-10 14:12         ` Andrew Lunn
2025-04-10 14:41           ` Jeff Layton
2025-04-13 11:40           ` Jeff Layton
2025-04-13 19:32             ` Andrew Lunn
2025-04-14 12:20               ` Jeff Layton
2025-04-14 12:46                 ` Andrew Lunn
2025-04-14 12:48                   ` Jeff Layton

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=20250410042729.28604-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.