Linux Media Controller development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Prajval Chaudhary <prajvalchaudhari733@gmail.com>
Cc: Andy Shevchenko <andy@kernel.org>,
	Hans de Goede <hansg@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev
Subject: Re: [PATCH v4 2/2] staging: media: atomisp: Remove dbg_level and dbg_func module parameters
Date: Tue, 21 Jul 2026 23:55:29 +0300	[thread overview]
Message-ID: <al_cwbjvaAJ1mOC9@ashevche-desk.local> (raw)
In-Reply-To: <20260721163533.15888-3-prajvalchaudhari733@gmail.com>

On Tue, Jul 21, 2026 at 10:05:32PM +0530, Prajval Chaudhary wrote:
> Remove the 'dbg_level' and 'dbg_func' module parameters to align the
> driver's debug facility with standard Linux kernel APIs (printk/vprintk).
> 
> The internal logic relying on custom debug parameters has been updated
> so that message logging and function tracing no longer depend on exposed
> userspace module parameters.

...

>  /* cross component debug message flag */
> -int dbg_level;
> -module_param(dbg_level, int, 0644);
> -MODULE_PARM_DESC(dbg_level, "debug message level (default:0)");

And what level is the default now? What the difference with the other levels?

>  /* log function switch */
> -int dbg_func = 1;
> -module_param(dbg_func, int, 0644);
> -MODULE_PARM_DESC(dbg_func,
> -		 "log function switch non/printk (default:printk)");

What are the other options?

...

>  /*! \file */
> -

Stray blank line removal.

> +#include <linux/printk.h>

Locate it in the linux/*.h group below. But I agree that at some point this
custom type_support should be moved down.

>  #include <type_support.h>
>  #include <linux/stdarg.h>
>  #include <linux/bits.h>

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-07-21 20:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 16:35 [PATCH v4 0/2] staging: media: atomisp: Cleanup unused module parameters Prajval Chaudhary
2026-07-21 16:35 ` [PATCH v4 1/2] staging: media: atomisp: Remove pad_w and pad_h " Prajval Chaudhary
2026-10-03 21:27   ` Sakari Ailus
2026-07-21 16:35 ` [PATCH v4 2/2] staging: media: atomisp: Remove dbg_level and dbg_func " Prajval Chaudhary
2026-07-21 20:55   ` Andy Shevchenko [this message]
2026-10-03 21:30   ` Sakari Ailus
2026-07-21 20:56 ` [PATCH v4 0/2] staging: media: atomisp: Cleanup unused " Andy Shevchenko

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=al_cwbjvaAJ1mOC9@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=prajvalchaudhari733@gmail.com \
    --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