From: Sakari Ailus <sakari.ailus@iki.fi>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Martin Weidenauer <martin@weidenauer.cc>,
hansg@kernel.org, mchehab@kernel.org,
sakari.ailus@linux.intel.com, andy@kernel.org,
gregkh@linuxfoundation.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
~lkcamp/patches@lists.sr.ht, koike@igalia.com
Subject: Re: [PATCH] staging: atomisp: isp: fix open brace on new line
Date: Sat, 18 Apr 2026 12:07:20 +0300 [thread overview]
Message-ID: <aeNJyPr_2tW8CFJa@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <aHYJD4aJDOxZJmQT@smile.fi.intel.com>
Hi,
On Tue, Jul 15, 2025 at 10:53:51AM +0300, Andy Shevchenko wrote:
> On Mon, Jul 14, 2025 at 05:34:09PM +0200, Martin Weidenauer wrote:
> > Fix checkpatch error "ERROR: that open brace { should be on the previous line"
> > in ia_css_dvs.host.c:277.
>
> ...
>
>
> > Hi, I hope this should fix the indentation problems.
>
> Missed versioning and changelog, but otherwise okay.
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
This is addressed (among other things) by commit
0d321169bda4ada7ffc9a1ff6fdcd5e753f82878 in my atomisp branch.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2026-04-18 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 15:34 [PATCH] staging: atomisp: isp: fix open brace on new line Martin Weidenauer
2025-07-14 17:47 ` Andy Shevchenko
2025-07-14 19:38 ` Martin Weidenauer
2025-07-14 21:38 ` Andy Shevchenko
2025-07-14 21:54 ` Martin Weidenauer
2025-07-15 6:57 ` Andy Shevchenko
2025-07-15 7:04 ` Greg KH
2025-07-15 7:26 ` Andy Shevchenko
2025-07-15 7:53 ` Andy Shevchenko
2026-04-18 9:07 ` Sakari Ailus [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-14 13:19 Martin Weidenauer
2025-07-14 13:24 ` Greg KH
2025-07-14 13:51 ` Martin Weidenauer
2025-07-14 15:27 ` 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=aeNJyPr_2tW8CFJa@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=koike@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@weidenauer.cc \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=~lkcamp/patches@lists.sr.ht \
/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