From: Dan Carpenter <dan.carpenter@linaro.org>
To: Omer El Idrissi <omer.e.idrissi@gmail.com>
Cc: sakari.ailus@linux.intel.com, mchehab@kernel.org,
gregkh@linuxfoudnation.org, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: media: ipu3: fix function argument alignment
Date: Wed, 28 Jan 2026 13:03:51 +0300 [thread overview]
Message-ID: <aXnfBw6gjULv5xW3@stanley.mountain> (raw)
In-Reply-To: <20260125134900.9964-1-omer.e.idrissi@gmail.com>
On Sun, Jan 25, 2026 at 02:49:00PM +0100, Omer El Idrissi wrote:
> Fix alignment of function arguments to match kernel coding
> style as reported by checkpatch.pl
>
> Signed-off-by: Omer El Idrissi <omer.e.idrissi@gmail.com>
> ---
> drivers/staging/media/ipu3/ipu3.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/media/ipu3/ipu3.c b/drivers/staging/media/ipu3/ipu3.c
> index bdf5a457752b..c34ff01484e1 100644
> --- a/drivers/staging/media/ipu3/ipu3.c
> +++ b/drivers/staging/media/ipu3/ipu3.c
> @@ -151,7 +151,7 @@ static int imgu_dummybufs_init(struct imgu_device *imgu, unsigned int pipe)
>
> /* May be called from atomic context */
> static struct imgu_css_buffer *imgu_dummybufs_get(struct imgu_device *imgu,
> - int queue, unsigned int pipe)
> + int queue, unsigned int pipe)
You should have only delete one space character but you accidentally
deleted two.
regards,
dan carpenter
> {
> unsigned int i;
> struct imgu_media_pipe *imgu_pipe = &imgu->imgu_pipe[pipe];
> --
> 2.51.0
>
next prev parent reply other threads:[~2026-01-28 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 13:49 [PATCH] staging: media: ipu3: fix function argument alignment Omer El Idrissi
2026-01-28 10:03 ` Dan Carpenter [this message]
2026-01-28 16:58 ` [PATCH v2] " Omer El Idrissi
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=aXnfBw6gjULv5xW3@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoudnation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=omer.e.idrissi@gmail.com \
--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