From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Oskar Ray-Frayssinet <rayfraytech@gmail.com>
Cc: hansg@kernel.org, gregkh@linuxfoundation.org, mchehab@kernel.org,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: atomisp: fix block comment style in circbuf.c
Date: Tue, 10 Mar 2026 15:21:34 +0200 [thread overview]
Message-ID: <abAa3mVvlmba16kd@kekkonen.localdomain> (raw)
In-Reply-To: <20260309213024.5733-1-rayfraytech@gmail.com>
Hi Oskar,
On Mon, Mar 09, 2026 at 10:30:24PM +0100, Oskar Ray-Frayssinet wrote:
A more elaborate description of the patch goes here.
> Signed-off-by: Oskar Ray-Frayssinet <rayfraytech@gmail.com>
> ---
> .../media/atomisp/pci/base/circbuf/src/circbuf.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/media/atomisp/pci/base/circbuf/src/circbuf.c b/drivers/staging/media/atomisp/pci/base/circbuf/src/circbuf.c
> index cb34d0b5abb5..db0b76ea4a29 100644
> --- a/drivers/staging/media/atomisp/pci/base/circbuf/src/circbuf.c
> +++ b/drivers/staging/media/atomisp/pci/base/circbuf/src/circbuf.c
> @@ -192,9 +192,9 @@ uint32_t ia_css_circbuf_peek_from_start(ia_css_circbuf_t *cb, int offset)
> * Please refer to "ia_css_circbuf.h" for details.
> */
> bool ia_css_circbuf_increase_size(
> - ia_css_circbuf_t *cb,
> - unsigned int sz_delta,
> - ia_css_circbuf_elem_t *elems)
> + ia_css_circbuf_t *cb,
> + unsigned int sz_delta,
> + ia_css_circbuf_elem_t *elems)
You could improve this more.
> {
> u8 curr_size;
> u8 curr_end;
> @@ -206,7 +206,8 @@ bool ia_css_circbuf_increase_size(
> curr_size = cb->desc->size;
> curr_end = cb->desc->end;
> /* We assume cb was pre defined as global to allow
> - * increase in size */
> + * increase in size
> + */
> /* FM: are we sure this cannot cause size to become too big? */
> if (((uint8_t)(cb->desc->size + (uint8_t)sz_delta) > cb->desc->size) &&
> ((uint8_t)sz_delta == sz_delta))
> @@ -215,12 +216,14 @@ bool ia_css_circbuf_increase_size(
> return false; /* overflow in size */
>
> /* If elems are passed update them else we assume its been taken
/*
* Multi-line
* comment.
*/
> - * care before calling this function */
> + * care before calling this function
> + */
> if (elems) {
> /* cb element array size will not be increased dynamically,
> * but pointers to new elements can be added at the end
> * of existing pre defined cb element array of
> - * size >= new size if not already added */
> + * size >= new size if not already added
> + */
> for (i = curr_size; i < cb->desc->size; i++)
> cb->elems[i] = elems[i - curr_size];
> }
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-03-10 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 21:30 [PATCH] staging: atomisp: fix block comment style in circbuf.c Oskar Ray-Frayssinet
2026-03-10 13:21 ` Sakari Ailus [this message]
2026-03-10 15:16 ` [PATCH v2] staging: media: " Oskar Ray-Frayssinet
2026-03-10 15:44 ` Andy Shevchenko
2026-03-10 19:15 ` [PATCH v3] " Oskar Ray-Frayssinet
2026-04-16 11:29 ` Sakari Ailus
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=abAa3mVvlmba16kd@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--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=rayfraytech@gmail.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