From: Daniel Baluta <daniel.baluta@nxp.com>
To: Kalyani Patra <kalyanipatra2003@gmail.com>,
Hans de Goede <hansg@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Andy Shevchenko <andy@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Simona Toaca <simona.toaca@nxp.com>,
d-gole@ti.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v2] staging: atomisp: fix brace style and trailing whitespace in isp_param.c
Date: Wed, 11 Mar 2026 17:20:45 +0200 [thread overview]
Message-ID: <a26ba4c7-05d9-4df0-b4ec-1a82d2df075e@nxp.com> (raw)
In-Reply-To: <20260311151302.105992-1-kalyanipatra2003@gmail.com>
On 3/11/26 17:13, Kalyani Patra wrote:
> Fix checkpatch errors related to brace placement and remove trailing
> whitespace in isp_param.c.
>
> Reported by scripts/checkpatch.pl.
>
> Signed-off-by: Kalyani Patra <kalyanipatra2003@gmail.com>
> ---
Please keep in mint that when submitting a patch you need to start with version 1,
saying [PATCH]... it is enough for people to understand is v1.
Now, even if we did an internal review until v2 community doesn't know that and you need
to reset your counting.
Otherwise, people will ask you where is v1 (plus where is the changelog for v1->v2).
As now this is clear, I hope community can ignore [PATCH v2] in the subject as git tools will do
when applying the patch.
With that,
Reviewed-by: Daniel Baluta <daniel.baluta@nxp.com>
next prev parent reply other threads:[~2026-03-11 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 15:13 [PATCH v2] staging: atomisp: fix brace style and trailing whitespace in isp_param.c Kalyani Patra
2026-03-11 15:20 ` Daniel Baluta [this message]
2026-03-11 15:22 ` Kalyani patra
2026-03-17 8:31 ` Sakari Ailus
[not found] ` <CACjYBvir9vnXqH4HVXKqMs-pmqTWjs3wA92WH9_KUpwSr3KD8Q@mail.gmail.com>
2026-03-17 9:33 ` Sakari Ailus
2026-03-17 17:09 ` Kalyani patra
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=a26ba4c7-05d9-4df0-b4ec-1a82d2df075e@nxp.com \
--to=daniel.baluta@nxp.com \
--cc=andy@kernel.org \
--cc=d-gole@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=kalyanipatra2003@gmail.com \
--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 \
--cc=simona.toaca@nxp.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