From: Dan Carpenter <dan.carpenter@linaro.org>
To: Anushka Badhe <anushkabadhe@gmail.com>
Cc: hansg@kernel.org, mchehab@kernel.org, gregkh@linuxfoundation.org,
andy@kernel.org, sakari.ailus@linux.intel.com,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: atomisp: vf_1.0: fix open brace placement
Date: Mon, 23 Mar 2026 12:52:14 +0300 [thread overview]
Message-ID: <acENTtTMsD-xca2O@stanley.mountain> (raw)
In-Reply-To: <20260323093024.38704-1-anushkabadhe@gmail.com>
On Mon, Mar 23, 2026 at 03:00:24PM +0530, Anushka Badhe wrote:
> Fix open brace placement on function definitions and control statements to comply with kernel coding style.
>
Line wrap your commit message at 74 characters. Also run your
patches through checkpatch.pl. (Ignore the space character
warning since that was there in the original code).
regards,
dan carpenter
next prev parent reply other threads:[~2026-03-23 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 9:30 [PATCH] staging: atomisp: vf_1.0: fix open brace placement Anushka Badhe
2026-03-23 9:52 ` Dan Carpenter [this message]
2026-03-23 10:21 ` [PATCH v2] " Anushka Badhe
2026-03-23 10:45 ` Dan Carpenter
2026-03-23 11:09 ` 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=acENTtTMsD-xca2O@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=andy@kernel.org \
--cc=anushkabadhe@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@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