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 0/2] staging: media: atomisp: Cleanup unused module parameters
Date: Tue, 21 Jul 2026 23:56:53 +0300 [thread overview]
Message-ID: <al_dFbMRoe__5-EP@ashevche-desk.local> (raw)
In-Reply-To: <20260721163533.15888-1-prajvalchaudhari733@gmail.com>
On Tue, Jul 21, 2026 at 10:05:30PM +0530, Prajval Chaudhary wrote:
> This series cleans up unused module parameters from the atomisp driver.
>
> Patch 1 removes unused 'pad_w' and 'pad_h' module parameters.
> Patch 2 removes unused 'dbg_level' and 'dbg_func' module parameters,
> and updates ia_css_debug_vdtrace() to filter trace logging to WARNING
> level or below to avoid potential kernel log flooding.
Have you run (or simulate behaviour of) this driver? Can you show the difference
in the debug output before and after these patches?
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-07-21 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 16:35 Prajval Chaudhary
2026-07-21 16:35 ` [PATCH v4 1/2] staging: media: atomisp: Remove pad_w and pad_h " Prajval Chaudhary
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
2026-07-21 20:56 ` Andy Shevchenko [this message]
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_dFbMRoe__5-EP@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
all inboxes | Powered by JetHome®