From: Prajval Chaudhary <prajvalchaudhari733@gmail.com>
To: Hans de Goede <hansg@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andy Shevchenko <andy@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Prajval Chaudhary <prajvalchaudhari733@gmail.com>
Subject: [PATCH 0/2] staging: media: atomisp: Clean up unnecessary module parameters
Date: Sun, 19 Jul 2026 19:33:48 +0530 [thread overview]
Message-ID: <20260719140350.8266-1-prajvalchaudhari733@gmail.com> (raw)
This patch series addresses the 'Remove unnecessary/unwanted module
parameters' task listed in the atomisp driver's TODO file.
The first patch removes the unused debug parameters along with the
user-facing pad_w and pad_h parameters to safeguard hardware padding
boundaries. The second patch converts the remaining internal usages
of pad_w and pad_h to const configurations to enable compiler
optimizations and enforce type safety.
Prajval Chaudhary (2):
staging: media: atomisp: Remove unused and unwanted debug module
parameters
staging: media: atomisp: Mark pad_w and pad_h as const constants
.../media/atomisp/pci/atomisp_common.h | 6 ++----
.../staging/media/atomisp/pci/atomisp_v4l2.c | 19 ++-----------------
2 files changed, 4 insertions(+), 21 deletions(-)
--
2.34.1
next reply other threads:[~2026-07-19 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 14:03 Prajval Chaudhary [this message]
2026-07-19 14:03 ` [PATCH 1/2] staging: media: atomisp: Remove unused and unwanted debug module parameters Prajval Chaudhary
2026-07-19 17:05 ` Andy Shevchenko
2026-07-20 10:38 ` Dan Carpenter
2026-07-20 10:59 ` Andy Shevchenko
2026-07-19 14:03 ` [PATCH 2/2] staging: media: atomisp: Mark pad_w and pad_h as const constants Prajval Chaudhary
2026-07-19 17:02 ` [PATCH 0/2] staging: media: atomisp: Clean up unnecessary module parameters 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=20260719140350.8266-1-prajvalchaudhari733@gmail.com \
--to=prajvalchaudhari733@gmail.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=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