From: Jakub Kicinski <kuba@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Qasim Ijaz <qasdev00@gmail.com>,
Nathan Chancellor <nathan@kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5 06/10] ref_tracker: automatically register a file in debugfs for a ref_tracker_dir
Date: Tue, 29 Apr 2025 16:28:02 -0700 [thread overview]
Message-ID: <20250429162802.1cfc3965@kernel.org> (raw)
In-Reply-To: <20250428-reftrack-dbgfs-v5-6-1cbbdf2038bd@kernel.org>
On Mon, 28 Apr 2025 11:26:29 -0700 Jeff Layton wrote:
> +/**
> + * ref_tracker_dir_debugfs - create debugfs file for ref_tracker_dir
> + * @dir: ref_tracker_dir to be associated with debugfs file
> + * @fmt: format string for filename
> + * @...: arguments for the format string
> + *
> + * Call this function to create a debugfs file for your ref_tracker_dir that
> + * displays the current refcounts for the object. It will be automatically
> + * removed when the ref_tracker_dir exits. The filename must be unique. If
> + * the creation fails then the pr_warn will be emitted.
> + */
> +void ref_tracker_dir_debugfs(struct ref_tracker_dir *dir)
lib/ref_tracker.c:374: warning: Excess function parameter 'fmt' description in 'ref_tracker_dir_debugfs'
lib/ref_tracker.c:374: warning: Excess function parameter '...' description in 'ref_tracker_dir_debugfs'
next prev parent reply other threads:[~2025-04-29 23:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 18:26 [PATCH v5 00/10] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir Jeff Layton
2025-04-28 18:26 ` [PATCH v5 01/10] ref_tracker: don't use %pK in pr_ostream() output Jeff Layton
2025-04-28 18:26 ` [PATCH v5 02/10] ref_tracker: add a top level debugfs directory for ref_tracker Jeff Layton
2025-04-28 18:26 ` [PATCH v5 03/10] ref_tracker: have callers pass output function to pr_ostream() Jeff Layton
2025-04-28 18:26 ` [PATCH v5 04/10] ref_tracker: allow pr_ostream() to print directly to a seq_file Jeff Layton
2025-04-29 23:27 ` Jakub Kicinski
2025-04-30 2:18 ` Jeff Layton
2025-04-30 14:23 ` Jakub Kicinski
2025-04-28 18:26 ` [PATCH v5 05/10] ref_tracker: add a static classname string to each ref_tracker_dir Jeff Layton
2025-04-28 18:26 ` [PATCH v5 06/10] ref_tracker: automatically register a file in debugfs for a ref_tracker_dir Jeff Layton
2025-04-29 23:28 ` Jakub Kicinski [this message]
2025-04-28 18:26 ` [PATCH v5 07/10] ref_tracker: add a way to create a symlink to the ref_tracker_dir debugfs file Jeff Layton
2025-04-28 18:26 ` [PATCH v5 08/10] net: add symlinks to ref_tracker_dir for netns Jeff Layton
2025-04-28 18:26 ` [PATCH v5 09/10] i915: add ref_tracker_dir symlinks for each tracker Jeff Layton
2025-04-28 18:26 ` [PATCH v5 10/10] ref_tracker: eliminate the ref_tracker_dir name field Jeff Layton
2025-04-29 23:26 ` [PATCH v5 00/10] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir 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=20250429162802.1cfc3965@kernel.org \
--to=kuba@kernel.org \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jlayton@kernel.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qasdev00@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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).