public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "luo.liu.linux" <luo.liu.linux@163.com>
To: sakari.ailus@linux.intel.com, mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re:[PATCH v2] media:v4l2-async:add debugfs under CONFIG_DEBUG_FS
Date: Fri, 6 Mar 2026 17:41:17 +0800 (CST)	[thread overview]
Message-ID: <500865d6.8b0f.19cc285d65e.Coremail.luo.liu.linux@163.com> (raw)
In-Reply-To: <20260121031456.1125096-1-luo.liu.linux@163.com>

 
 Hello Sakari and Mauro,
  
     Gentle ping ....


At 2026-01-21 11:14:56, "luo.liu" <luo.liu.linux@163.com> wrote:
>All debugfs-related code is guarded by CONFIG_DEBUG_FS to avoid
>bloating the kernel when debugfs is disabled.
>
>Signed-off-by: luo.liu <luo.liu.linux@163.com>
>---
> drivers/media/v4l2-core/v4l2-async.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
>diff --git a/drivers/media/v4l2-core/v4l2-async.c b/drivers/media/v4l2-core/v4l2-async.c
>index 1c08bba9ecb9..f6a1a57149ba 100644
>--- a/drivers/media/v4l2-core/v4l2-async.c
>+++ b/drivers/media/v4l2-core/v4l2-async.c
>@@ -947,6 +947,7 @@ v4l2_async_nf_name(struct v4l2_async_notifier *notifier)
> 		return "nil";
> }
> 
>+#ifdef CONFIG_DEBUG_FS
> static int pending_subdevs_show(struct seq_file *s, void *data)
> {
> 	struct v4l2_async_notifier *notif;
>@@ -967,20 +968,25 @@ static int pending_subdevs_show(struct seq_file *s, void *data)
> DEFINE_SHOW_ATTRIBUTE(pending_subdevs);
> 
> static struct dentry *v4l2_async_debugfs_dir;
>+#endif
> 
> static int __init v4l2_async_init(void)
> {
>+#ifdef CONFIG_DEBUG_FS
> 	v4l2_async_debugfs_dir = debugfs_create_dir("v4l2-async", NULL);
> 	debugfs_create_file("pending_async_subdevices", 0444,
> 			    v4l2_async_debugfs_dir, NULL,
> 			    &pending_subdevs_fops);
> 
>+#endif
> 	return 0;
> }
> 
> static void __exit v4l2_async_exit(void)
> {
>+#ifdef CONFIG_DEBUG_FS
> 	debugfs_remove_recursive(v4l2_async_debugfs_dir);
>+#endif
> }
> 
> subsys_initcall(v4l2_async_init);
>
>base-commit: d08c85ac8894995d4b0d8fb48d2f6a3e53cd79ab
>-- 
>2.25.1

  reply	other threads:[~2026-03-06  9:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21  3:14 [PATCH v2] media:v4l2-async:add debugfs under CONFIG_DEBUG_FS luo.liu
2026-03-06  9:41 ` luo.liu.linux [this message]
2026-03-11  9:20   ` Sakari Ailus
2026-03-11  9:42     ` luo.liu.linux
2026-03-12  7:06     ` luo.liu.linux
2026-03-11  7:04 ` Sakari Ailus
2026-03-11  8:58   ` luo.liu.linux
2026-03-11  9:16     ` Sakari Ailus

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=500865d6.8b0f.19cc285d65e.Coremail.luo.liu.linux@163.com \
    --to=luo.liu.linux@163.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.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