mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: "luo.liu" <luo.liu.linux@163.com>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media:v4l2-async:add debugfs under CONFIG_DEBUG_FS
Date: Wed, 11 Mar 2026 09:04:28 +0200	[thread overview]
Message-ID: <abET_OcHYr5_wpdK@kekkonen.localdomain> (raw)
In-Reply-To: <20260121031456.1125096-1-luo.liu.linux@163.com>

Hi Luo,

Thanks for the patch.

On Wed, Jan 21, 2026 at 11:14:56AM +0800, luo.liu 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

This part seems reasonable...

>  
>  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
>  }

But are the two latter #if's useful? Looks like the compiler should
optimise these out...

>  
>  subsys_initcall(v4l2_async_init);
> 
> base-commit: d08c85ac8894995d4b0d8fb48d2f6a3e53cd79ab

-- 
Kind regards,

Sakari Ailus

  parent reply	other threads:[~2026-03-11  7:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21  3:14 luo.liu
2026-03-06  9:41 ` luo.liu.linux
2026-03-11  9:20   ` [PATCH " 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 [this message]
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=abET_OcHYr5_wpdK@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=luo.liu.linux@163.com \
    --cc=mchehab@kernel.org \
    /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

all inboxes | Powered by JetHome®