From: Dan Carpenter <dan.carpenter@linaro.org>
To: Giorgi Tchankvetadze <giorgitchankvetadze1997@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: media: atomisp: pipe_stagedesc: Fix leading space indentation
Date: Sat, 7 Mar 2026 17:33:47 +0300 [thread overview]
Message-ID: <aaw3S6WjumRCPJ2k@stanley.mountain> (raw)
In-Reply-To: <20260307120232.74846-3-giorgitchankvetadze1997@gmail.com>
On Sat, Mar 07, 2026 at 04:02:34PM +0400, Giorgi Tchankvetadze wrote:
> Fix lines starting with spaces instead of tabs to comply with the
> kernel coding style.
>
> No functional change.
>
> Signed-off-by: Giorgi Tchankvetadze <giorgitchankvetadze1997@gmail.com>
> ---
> .../pci/camera/pipe/src/pipe_stagedesc.c | 32 +++++++++----------
> 1 file changed, 16 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/staging/media/atomisp/pci/camera/pipe/src/pipe_stagedesc.c b/drivers/staging/media/atomisp/pci/camera/pipe/src/pipe_stagedesc.c
> index a9f736398f50..8e31981f31b4 100644
> --- a/drivers/staging/media/atomisp/pci/camera/pipe/src/pipe_stagedesc.c
> +++ b/drivers/staging/media/atomisp/pci/camera/pipe/src/pipe_stagedesc.c
> @@ -9,11 +9,11 @@
> #include "ia_css_debug.h"
>
> void ia_css_pipe_get_generic_stage_desc(
> - struct ia_css_pipeline_stage_desc *stage_desc,
> - struct ia_css_binary *binary,
> - struct ia_css_frame *out_frame[],
> - struct ia_css_frame *in_frame,
> - struct ia_css_frame *vf_frame)
> + struct ia_css_pipeline_stage_desc *stage_desc,
> + struct ia_css_binary *binary,
> + struct ia_css_frame *out_frame[],
> + struct ia_css_frame *in_frame,
> + struct ia_css_frame *vf_frame)
Same feedback.
regards,
dan carpenter
prev parent reply other threads:[~2026-03-07 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 12:02 [PATCH] staging: media: atomisp: pipe_stagedesc: Fix leading space indentation Giorgi Tchankvetadze
2026-03-07 14:33 ` Dan Carpenter [this message]
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=aaw3S6WjumRCPJ2k@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=giorgitchankvetadze1997@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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