From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Bohdan D. Marcus" <bohdandmarcus@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] staging: media: atomisp: clean up block comment formatting in headers
Date: Sun, 12 Jul 2026 13:34:00 +0300 [thread overview]
Message-ID: <alNtmD6nYCZoOCaA@ashevche-desk.local> (raw)
In-Reply-To: <20260710120254.23565-2-bohdandmarcus@gmail.com>
On Fri, Jul 10, 2026 at 03:02:53PM +0300, Bohdan D. Marcus wrote:
> Fix block comment formatting issues in several header files to comply
> with the Linux kernel coding style. Specifically:
> - Move trailing '*/' to a separate line.
> - Align '*' on subsequent lines of block comments.
> - Reformat excessively long lines and remove Doxygen-style tags.
...
> /* Purpose of mutex is to protect and serialize use of isp data
> - * structures and css API calls. */
> + * structures and css API calls.
> + */
This still has a problem with the style.
...
Have you checked patches by Ricardo Ribalda?
...
Sakari, may you apply Ricardo's first two patches at least, please?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-07-12 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 12:02 [PATCH v2 0/2] staging: media: atomisp: clean up comment formatting and grammar Bohdan D. Marcus
2026-07-10 12:02 ` [PATCH v2 1/2] staging: media: atomisp: clean up block comment formatting in headers Bohdan D. Marcus
2026-07-12 10:34 ` Andy Shevchenko [this message]
2026-07-12 13:02 ` Bohdan Derkach
2026-07-10 12:02 ` [PATCH v2 2/2] staging: media: atomisp: fix grammar and punctuation in inline comments Bohdan D. Marcus
2026-07-12 10:35 ` 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=alNtmD6nYCZoOCaA@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=bohdandmarcus@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--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
all inboxes | Powered by JetHome®